Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 22379 by john.leidegren: Fast JSON responses ends up as part of
the HTTP response header
http://code.google.com/p/chromium/issues/detail?id=22379
Chrome Version : 3.0.195.21
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 4:
Firefox 3.x: OK
IE 7: OK
IE 8: OK
What steps will reproduce the problem?
1. A XMLHttpRequest json response that returns something really fast will
not return the response body as responseText.
2. A sleep(1000) on the server will basically prevent the problem. However,
that's not correct behavior.
What is the expected result?
The JSON response will be read and the XMLHttpRequest.responseText will be
readable.
What happens instead?
There's some sort of synchronization issue in Google Chrome, occasionally
and consequently the XMLHttpRequest.responseText property is undefined when
it should return some actual content.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
