Forum Discussion
Craig_Jackson_2
Nimbostratus
NimbostratusSpurious CRLF before HTTP verb
We're running into a problem with a spurious \r\n being sent to the server immediately preceding a HTTP verb. This is in a OneConnect environment.
The problem occurs because IE (6 and 7 at ...
Craig_Jackson_2Nimbostratus
NimbostratusJust checked the HTTP 1/1 RFC. It suggests that it's something that the client MAY do. It appears that the only way for the the server to stop it is to close the connection after delivering the response to the first request. (The client is suppose to be prepared to retry.)
So I suppose that the "pipelining" switch could cause the LTM to close the connection if a request was received before a previous response had been delivered. However, it would seem that such a switch would allow connection reuse if the requests were not received prematurely. (I.e. if a strict request/response discipline was maintained over the reused connection.) Is this correct? If so, how would that help my connection-reuse problem?
