Conversation
|
Hi @ac000, |
|
True, as the code currently stands we are assuming that we only upgrade to websockets. I guess strictly speaking we should check that's the case... but I would probably do that as a separate patch to this as this patch simply fixes the problem of determining if we are upgrading the connection. |
|
Actually we do already check the If we find This combination is then checked for in if (h1p->connection_upgrade && h1p->upgrade_websocket) {So I think we're all good, right? |
|
Correct. |
|
Not sure it makes a lot of sense, but sure, we can do that... |
|
Firefox (going back a couple of years at least) was unable to open a WebSocket connection to Unit due to it sending a Connection header of Connection: keep-alive, Upgrade However in Unit we were expecting only a single value in the header. Fix the 'Connection' parsing in nxt_h1p_connection() to address this. Closes: nginx#772 Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
aede3ed to
df62a2a
Compare
|
Rebased with master |
Uh oh!
There was an error while loading. Please reload this page.