Re: [users@httpd] RE: Web sockets & proxypass - No protocol handler was valid for the URL

2017-09-10 Thread Damien Clark
Hi Eric, Thanks so much for taking the time to generate a working config. Initially it didn’t work (the RewriteCond was not matching), so I performed a packet capture on the request leaving my browser, and compared it with a packet capture arriving at the apache process. This revealed that

Re: [users@httpd] RE: Web sockets & proxypass - No protocol handler was valid for the URL

2017-09-10 Thread Damien Clark
G’day Eric, Thanks so much for taking the time to generate a working config. Initially it didn’t work. So I performed a packet capture outbound from my browser (which showed the Upgrade header), and also inbound to the apache process and determined that the ‘Upgrade’ header was lost somewhere

Re: [users@httpd] RE: Web sockets & proxypass - No protocol handler was valid for the URL

2017-09-07 Thread Damien Clark
> On 8 Sep 2017, at 2:04 am, Eric Covener <cove...@gmail.com> wrote: > > On Thu, Sep 7, 2017 at 10:19 AM, Damien Clark <damo.cla...@gmail.com> wrote: >> >>> On 7 Sep 2017, at 11:53 pm, Eric Covener <cove...@gmail.com> wrote: >>> >>

Re: [users@httpd] RE: Web sockets & proxypass - No protocol handler was valid for the URL

2017-09-07 Thread Damien Clark
> On 7 Sep 2017, at 11:53 pm, Eric Covener wrote: > >> >> I am wondering whether the use of a rewriterule with the “P” flag is the >> reason the upgrade header hasn’t been included. I wonder this because it is >> pretty widely reported to work fine when using ProxyPass to

Re: [users@httpd] RE: Web sockets & proxypass - No protocol handler was valid for the URL

2017-09-07 Thread Damien Clark
> On 7 Sep 2017, at 11:53 pm, Eric Covener wrote: > >> >> I am wondering whether the use of a rewriterule with the “P” flag is the >> reason the upgrade header hasn’t been included. I wonder this because it is >> pretty widely reported to work fine when using ProxyPass to

[users@httpd] RE: Web sockets & proxypass - No protocol handler was valid for the URL

2017-09-07 Thread Damien Clark
Hi Eric/Adam, Just reviving an old thread. Here is the full thread archive if it helps. http://apache-http-server.18135.x6.nabble.com/Web-sockets-amp-proxypass-No-protocol-handler-was-valid-for-the-URL-td5033887.html I am using Apache virtual host as frontend, and Node.js as backend running