Hi All i am trying to figure out as to why the client after receiving 302 is delaying to close the connection and initiate new one for the url in Location header.
Basically the traffic to the Web App (via load balancer is as follows):
1) the client posts with a HTTP POST containing their login details
2) the server accepts that message, commits it, and responds to the client by sending a HTTP 302 redirect to a page called ....
3) The client when receiving the 302 would close its TCP session, and reestablish a new one and send a HTTP GET for the new URL provided in the 302 redirect.
4) Client confirms receiving 302 and :
The main question is as to why after client’s receiving 302 is not terminating existing connection …?
Any ideas ?
asked 07 Aug ‘12, 15:21
well, hard to say without any information about the client beeing used... Please add this:
answered 07 Aug '12, 17:00
Kurt Knochner ♦
edited 07 Aug '12, 17:00
My guess would be that the 302 response is not correct. Is there a Content-Length header? And does it correctly state the length of the 302 response? Is Keep-Alive used by any chance? It's pretty hard to analyze this issue based on just a screenshot, that's why we all love to use Wireshark :-)
As you obfuscated some of the info, I assume you are not able to share the tracefiles? Are you able to send them privately to one or two persons? I'd be willing to have a quick look at them if you'd like.
answered 08 Aug '12, 02:21