Spurious CRLF before HTTP verb

Good to know that this worked out for you. Just to set things straight, turning off the pipelining should not have any performance for connections that don't pipeline the requests (they will get connection pooled / oneconnected just like all the requests). For the ones that do happen to pipeline, we will honor the first pipelined request but will close the connection when the response is sent. As you know from the RFC clients are supposed to re-try the requests (only non idempotent requests should be pipelined) therefore it should not break the application. It does however add the over head of the new connection especially if the virtual is shared with other applications that do proper pipelining.

 

 

The reason why I suggested this in the first place is because the irule necessary to do achieve this get a lot trickier than what you have. You can't solve this from HTTP because we deliberately prevent you from modifying data that's not part of the current request. Since the extra CRLF's 'appear' as data for the next request, the HTTP rules can’t touch it.

 

 

This does not mean that you can't do this though. You could hook into the TCP events and parse it before the HTTP layer has had a chance to process the data. I did not want to cross that bridge until you had a chance to try disabling pipeling. The only down side to this approach is that parsing data at the TCP layer will affect all traffic where as disabling the pipeling affects just the pipelined connections.

 

 

With that said, we are looking at fixing this in subsequest release. If you would like to track this fix or need it sooner go ahead and feel free to open a ticket with support and tell them bl0ndie sent you. In the mean time here is a similar example that demonstrates parsing at the TCP layer.

 

 

Click here