Am 08.02.2018 um 19:50 schrieb Mark Nenadov:
according to the docs, you can actually specify the protocol:
https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html :
"In fact the module can be used to upgrade to other protocols, you can set the
upgrade parameter in the ProxyPass directive
> according to the docs, you can actually specify the protocol:
>
> https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html :
>
> "In fact the module can be used to upgrade to other protocols, you can set
> the upgrade parameter in the ProxyPass directive to allow the module to
> accept oth
On Thu, Feb 8, 2018 at 1:33 PM, wrote:
> You are probably proxying with mod_proxy_wstunnel. It seems to me that
> "Upgrade: WebSocket" is hard-coded in that module.
>
> Regards,
>
> Rainer
Hi Rainer,
Thanks. Yes, I am using mod_proxy_wstunnel and it appears that that is
the issue.
~Mark
Hi Rainer, hi Mark,
Zitat von Rainer Jung :
Hi Mark,
Am 08.02.2018 um 16:49 schrieb Mark Nenadov:
Hello, I have an operational setup where Apache httpd is proxying
secure websockets traffic to an Apache Tomcat server. In other
words, I'm using ProxyPass to pass traffic along to a WSS url.
Hi Mark,
Am 08.02.2018 um 16:49 schrieb Mark Nenadov:
Hello, I have an operational setup where Apache httpd is proxying secure
websockets traffic to an Apache Tomcat server. In other words, I'm using
ProxyPass to pass traffic along to a WSS url.
I'm now having some issues trying to throw mod_
Hello, I have an operational setup where Apache httpd is proxying secure
websockets traffic to an Apache Tomcat server. In other words, I'm using
ProxyPass to pass traffic along to a WSS url.
I'm now having some issues trying to throw mod_headers into the mix. I'm
attempting to manipulate the "Upg
