Re: Inform backend about https for http2 connections

Hi, Am 07.08.2016 um 13:35 schrieb Matthias Fechner: I think the only possibilty whould then to define several backends on different ports and define there the h2c or h2 in the frontend configuration of nginx. Yes, because otherwise you have a problem on the nginx configuration as well:

Re: Inform backend about https for http2 connections

Am 06.08.2016 um 15:12 schrieb Neil - HAProxy List: > > if you can have the app not specify the scheme for the css etc. just use > > //site.com/path > or > /path if it is on the same site > as I do not develop the apps I cannot do it. The configuration how the return

Re: Inform backend about https for http2 connections

Am 06.08.2016 um 05:31 schrieb Igor Cicimov: > Afaik, since http2 is by default tls encrypted just by specifying h2 > as protocol to the backend should be enough i guess. this is not completely true. There is h2c which uses http2 without TLS. Gruß Matthias -- "Programming today is a race

Re: Inform backend about https for http2 connections

Hello if you can have the app not specify the scheme for the css etc. just use //site.com/path or /path if it is on the same site On 6 Aug 2016 04:33, "Igor Cicimov" wrote: > On 6 Aug 2016 1:31 am, "Matthias Fechner" wrote: > > > > Dear

Re: Inform backend about https for http2 connections

On 6 Aug 2016 1:31 am, "Matthias Fechner" wrote: > > Dear all, > > > I use haproxy in tcp mode to have http2 working. > Now I have the problem that the backend has to know if the connection > was encrypted or not (some websites using this information to add the > schema to css

Inform backend about https for http2 connections

Dear all, I use haproxy in tcp mode to have http2 working. Now I have the problem that the backend has to know if the connection was encrypted or not (some websites using this information to add the schema to css and javascript URIs). Normally I think a reqadd X-Forwarded-Proto:\ https should