forward HTTPS proxy | Re: The future of forward proxy servers in an http/2 over TLS world

( Kari Hurtta <> was bouncing after MX change.
  I reverted that change. )

Alex Rousskov <>

> To be more precise, the _browser_ needs that, but, yes, this is probably
> required, and that is exactly why I mentioned secure response signing
> (or something like that) as a prerequisite. The proxy would need to
> somehow forward origin's response signature or public certificate (at
> least). This is where an HTTP extension is required. Everything else is
> already supported (at the protocol level) AFAICT.

If HTTP/2 can be assumed for that https connection from browser to proxy,
the that extension can be new HTTP/2 frame. I think that this fits
to that place. 

Proxy sends that frame to browser before responses HEADERS frame.

This allows browser only show status after the fact. Browser
can not examine origin's certificate before it sends to proxy

       :method = GET
       :scheme = https
       :path = /
       :authority =

Willy Tarreau <>

> That's why I think that a technical solution like trusted proxies can be
> good. Let the user know whether he can have a TLS tunnel to the origin or
> has to retry in clear using "GET https://". Let's have the same warnings
> as when I'm asked whether or not I want to share my location with the site.

That can be new HTTP response code for CONNECT.

I think these are new protocol components which are needed on that solution.

/ Kari Hurtta

Received on Wednesday, 1 March 2017 19:27:35 UTC