The documentation states:
Proxying both HTTP and websockets at the same time, where the websockets URL's
are not websocket-only or not known in advance can be done by using the
RewriteRule directive to configure the websockets proxying:
ProxyPass / http://example.com:9080/
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "ws://example.com:9080/$1" [P,L]
However, I was wondering, whether the following is an equivalent directive
(just in a single line ;-)):
ProxyPass / http://example.com:9080/ upgrade=websocket
afaik the upgrade only takes place when it is requested by a header, unless
upgrade=NONE or upgrade=ANY is set.
Am I correct or are the not the same?
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Proxying both HTTP and websockets at the same time, where the websockets URL's
are not websocket-only or not known in advance can be done by using the
RewriteRule directive to configure the websockets proxying:
ProxyPass / http://example.com:9080/
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "ws://example.com:9080/$1" [P,L]
However, I was wondering, whether the following is an equivalent directive
(just in a single line ;-)):
ProxyPass / http://example.com:9080/ upgrade=websocket
afaik the upgrade only takes place when it is requested by a header, unless
upgrade=NONE or upgrade=ANY is set.
Am I correct or are the not the same?
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/