{"id":719,"date":"2012-11-01T00:00:00","date_gmt":"2012-11-01T00:00:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2012\/11\/01\/adx-http-packets-dropped-when-using-pipeling-and-csw\/"},"modified":"2023-02-24T08:59:33","modified_gmt":"2023-02-24T08:59:33","slug":"adx-http-packets-dropped-when-using-pipeling-and-csw","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/Brocade\/adx-http-packets-dropped-when-using-pipeling-and-csw.html","title":{"rendered":"Brocade ADX: HTTP Packets Dropped when using Pipelining & CSW"},"content":{"rendered":"
When enabling CSW and running HTTP pipelining you may experience a breakdown in your HTTP session.<\/p>\n
When enabling CSW on a Virtual Server pipelining is enabled on the designated port by default.
\nThe issue occurs when a\u00a0second GET request comes in before the first GET\/POST answer is fully received from the server (this could include a single ACK still pending), then the ADX drops the second request silently. The client will keep retransmitting the second request and then finally give up after some time.<\/p>\n
This issue is typically seen when using extremely long URI references.<\/p>\n
To resolve this issue there are 2 options.<\/p>\n
The “reset-pipeline-request” command (i.e \u201cport http keep-alive reset-pipeline-request\u201d) works around this issue by allowing the answer to the first request to complete (even if a second request comes in) and then resetting the connection. This in turn forces the client start a new connection for the second request.<\/p>\n
Note<\/em> : Should you enable ‘port <port> keep-alive reset-pipeline-request’ and then remove it using the command ‘no port <port> no-keep-alive’ (on the Virtual Server). You will need to ensure you re-enable keep-alive on the VIP using the command ‘port <port> keep-alive’.<\/p>\n","protected":false},"excerpt":{"rendered":" Symptoms When enabling CSW and running HTTP pipelining you may experience a breakdown in your HTTP session. Issue When enabling CSW on a Virtual Server pipelining is enabled on the designated port by default. The issue occurs when a\u00a0second GET request comes in before the first GET\/POST answer is fully received from the server (this … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[],"yoast_head":"\n