httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Covener <cove...@gmail.com>
Subject Re: [users@httpd] Web sockets & proxypass - No protocol handler was valid for the URL
Date Wed, 28 Dec 2016 14:36:46 GMT
On Wed, Dec 28, 2016 at 9:21 AM, Yann Ylavic <ylavic.dev@gmail.com> wrote:
> On Wed, Dec 28, 2016 at 1:32 PM, Adam Teale <adam@believe.tv> wrote:
>> more detail from the error log:
>>
>> [Wed Dec 28 09:31:05.974744 2016] [proxy:debug] [pid 27844]
>> mod_proxy.c(1198): [client 127.0.0.1:54002] AH01143: Running scheme wss
>> handler (attempt 0)
>
> Looks like the request is missing the "Upgrade: WebSocket" header,
> which mod_proxy_wstunnel requires.
>
> From your configuration:
>     ProxyPass /chat/stream/ wss://localhost:8000/chat/stream/
> it seems that /chat/stream/ is used for "normal" HTTP traffic (before
> the upgrade to WebSocket, possibly).
>
> Couldn't the pure WebSocket things be handled by another (inner) URL
> instead, so that the following could work:
>     ProxyPass /chat/stream/ https://localhost:8000/chat/stream/
>     ProxyPass /chat/stream/wss wss://localhost:8000/chat/stream/wss
>

Seems like we should setup wstunnel to go before http, so you could
then just configure both proxypasses and wstunnell would defer.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message