On Jun 14, 2014, at 7:06 AM, Eric Covener <[email protected]> wrote:
> On Fri, Jun 13, 2014 at 5:10 PM, <[email protected]> wrote: >> Allow for "magic" scheme "auto" which makes the scheme of >> the backend worker match whatever the scheme of the >> incoming request was... >> >> For example: >> >> ProxyPass / auto://foo.example.com/ >> >> If the incoming request is http:.../lala then >> the resultant will be http://foo.example.com/lala >> >> If it's wws:.../lolo then we'd send >> wws://foo.example.com/lolo > > > Does this work for websockets? Isn't the scheme http:// + Upgrade for > websockets? > > I thought "auto" would mean the handlers would second-guess the > scheme, but if we replace it in proxy_util.c they cannot do that > anymore. I thought the idea/issue was that we wanted, for example, an incoming http request to be handled by the http proxy scheme handler and if it was ws, to be handled by the ws scheme handler. This was not possible with the normal setup ProxyPass / http://foo.bar/ since all requests in this case would go to the http scheme handler (no matter what the incoming scheme was) as well as ProxyPass / ws://foo.bar/ Which would always go websockets, whether we wanted to or not. In other words, the incoming scheme determined the scheme we use on the backend, instead of it being "hard-coded" in the ProxyPass command. Not sure if I misunderstood or not :/
