Loading...
Loading...
During the Websocket handshake, if OneConnect is on, the Websocket header is set as "connection: close", then OneConnect will transform the header to be "X-Cnection: close". If the header is set as "connection: upgrade" as well as "connection: close", then OneConnect will transform both to be "X-Cnection: close" and "X-Cnection: upgrade", respectively. This causes some Websocket handshakes to fail.
Websocket handshakes fail resulting in connection reset.
Virtual server has HTTP and OneConnect profiles. The request has "Connection: close" and "Connection: upgrade" headers during the Websocket handshake.
Remove OneConnect or use iRule to re-add "Connection: upgrade"
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.