What does mean “may have to disable HTTP/2 in order to use this directive successfully on secure connections” for WebSocket? Then, I’ll have to downgrade the whole website to http/1.1 or only the WebSocket connection?
1 Like
I should probably reword that. Clients (browsers) should not use HTTP/2 to make websocket connections since h2 does not support protocol upgrade. You won’t have to worry about it unless the client is naive.
Thanks for the clear clarification. So, I’d have to leave my websocket caddyfile just like that and all the rest pages will work in general with h/2?
Yep, it should just work these days.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.