| Description: |
Calling ::websocket::open to connect to a websocket server sends a request with two Connection headers, one with "keep-alive" and another with the required "Upgrade".
There are websocket server implementations, namely civetweb, that do not expect multiple Connection headers and fail to upgrade to websocket.
There is a comment in websocket.tcl: "We force -keepalive to make sure the HTTP library does not insert a "Connection: close" directive in the headers..."
I understand that multiple Connection headers, or one header with multiple values, are not strictly violating the RFCs, but it sure feels unexpected to me.
|
| User Comments: |
kjnash added on 2022-10-10 16:20:55:
Please try http 2.10 from Tcl 8.7 trunk, which combines the two connection headers into one. The header sent is "Connection: upgrade, close" or "Connection: upgrade, keep-alive". In an upgrade request, the upgrade is not guaranteed. The value "close" or "keep-alive" tells the server what to do if it refuses the upgrade.
Please could you report whether this works with civetweb.
Some or all the bugfixes in http 2.10 will be backported to http 2.9 after the release of Tcl 8.7.
|