Re: Web sockets & proxypass - No protocol handler was valid for the URL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 28, 2016 at 1:32 PM, Adam Teale <adam@xxxxxxxxxx> 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
?

Regards,
Yann.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx




[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux