Loading...
Loading...
User had no way of knowing if one particular HTTP request has been responded to or not. A second response to one request would result in the rest of the connection or flow.
User has more options for multiple-response case.
If reset of the connection is not desired when making multiple responses to one HTTP request, use the new flag HTTP::has_responded to test before sending a HTTP response.
If reset of the connection is not desired when making multiple responses to one HTTP request, use the new flag HTTP::has_responded to test before sending a HTTP response.
None
Invoking HTTP::respond multiple times on the same request that triggered an HTTP::request event leads to TCL errors and RSTs. This can happen when there are multiple HTTP::request events attached to a virtual and each can invoke HTTP::respond. A new TCL command HTTP::has_response has been introduced that returns a boolean to indicate that HTTP::respond has already been invoked.
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.