Loading...
Loading...
In a keep alive transaction, the second or later request is not responded to, and the TCP connection is aborted.
Keep alive connections will not work consistently.
When an OWS closes a keep alive connection when it should not. This implies a possible a web server defect.
An iRule set that rewrites the Connection header on 1.1 version transactions may mitigate this, but at the cost of requiring a separate connection per requested object. If the web server error is intermittent, it may be more efficient to allow for the occasional retry.
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.