2025-01-18, 02:19 AM
(This post was last modified: 2025-01-19, 07:51 PM by shm0. Edited 5 times in total.)
Hi!
Thank you for this guide.
I have some questions!
Doesn't
http-response set-header Connection "keep-alive"
override
http-request set-header Connection "upgrade" if { req.hdr(Upgrade) -i WebSocket }
?
I tried to add some conditional checks (if !{ req.hdr(Upgrade) -i WebSocket }) to the set keep-alive rule but it still breaks websockets on some Smart TV apps.
And X-Frame-Options "SAMEORIGIN" breaks the LG WebOS App (Black screen after login).
And these acls:
jf hdr_connection_upgrade hdr_upgrade_websocket or jf -> will always evaluate to jf
emby hdr_connection_upgrade hdr_upgrade_websocket or emby -> will always evaluate to emby
making hdr_connection_upgrade hdr_upgrade_websocket obsolete.
I'm not sure if it is actually needed to set:
option http-server-close
option forwardfor
and some other options, in both the fronted and backend.
Is it actually a good idea to enable http-server-close for non websocket traffic?
The timeouts also seem quite high?
//edit
http-server-close actually seems to break websockets for me...
The only relevant timeout for websockets seems to be the tunnel one.
Thank you for this guide.
I have some questions!
Doesn't
http-response set-header Connection "keep-alive"
override
http-request set-header Connection "upgrade" if { req.hdr(Upgrade) -i WebSocket }
?
I tried to add some conditional checks (if !{ req.hdr(Upgrade) -i WebSocket }) to the set keep-alive rule but it still breaks websockets on some Smart TV apps.
And X-Frame-Options "SAMEORIGIN" breaks the LG WebOS App (Black screen after login).
And these acls:
jf hdr_connection_upgrade hdr_upgrade_websocket or jf -> will always evaluate to jf
emby hdr_connection_upgrade hdr_upgrade_websocket or emby -> will always evaluate to emby
making hdr_connection_upgrade hdr_upgrade_websocket obsolete.
I'm not sure if it is actually needed to set:
option http-server-close
option forwardfor
and some other options, in both the fronted and backend.
Is it actually a good idea to enable http-server-close for non websocket traffic?
The timeouts also seem quite high?
//edit
http-server-close actually seems to break websockets for me...
The only relevant timeout for websockets seems to be the tunnel one.