HTTPClient gets into a bad state after receiving a 204 (no content)
Reported by sjs | May 19th, 2011 @ 10:41 PM
After making a request that receives a response with status code 204 all subsequent requests result in status code 204 and empty responseText & responseData, even though the server is not sending such a response (100% certain about that).
I haven't reduced a test case but can do so if necessary. I'm pretty confident that is the issue, as soon as I had my server respond instead with some JSON like {status: 'ok'} and a 200 status code the exact same requests succeeded that had previously failed with 204 responses.
Comments and changes to this ticket
-
sjs May 19th, 2011 @ 10:43 PM
Note that I did not try making requests to any other host, so the issue may only manifest while talking to the same server. Again if necessary I'll attach a reduction, just let me know.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »