Enable serving with http/2 about symposium-2017

[praseodym]

No use, our reverse proxy doesn't do HTTP/2.

[martijnjanssen]

This was not an issue that needed fixing right away, this was something more long-term to think about. We don't want to be stuck without HTTP/2 forever.

[praseodym]

You weren't implying that by saying it would be "fairly easy".

[martijnjanssen]

Enabling for the container (this project only) would be fairly easy. Integrating it into the entire server architecture is something else entirely :)

[TimvdLippe]

https://symposium.ch.tudelft.nl/2017/ is now using H2 🎉

[martijnjanssen]

While this is true, the container does not use HTTP/2 right now, we will have to enable this in the nginx.conf.

[praseodym]

Doesn't matter: https://trac.nginx.org/nginx/ticket/923

[TimvdLippe]

@praseodym Could you elaborate? I am not familiar with the nginx proxy config. Does the linked ticket mean that it is already working or that something we require will not work?

[praseodym]

nginx doesn't (and in the foreseeable future won't) have support for using HTTP/2 to an upstream server when acting as a reverse proxy. Since the Symposium container will always be used behind a reverse proxy, it doesn't matter whether it supports HTTP/2 since that will never be used.