Bug 77500 - XMLHttpRequest is not returning server responses on uploads aborted from the server side
Summary: XMLHttpRequest is not returning server responses on uploads aborted from the ...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: XML (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.7
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-31 18:57 PST by Craig Yoshioka
Modified: 2012-02-01 14:18 PST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Yoshioka 2012-01-31 18:57:17 PST 
When uploading reasonably sized files (<100MB) the XHR will return the response code and abort if the server responds with an error code before the upload transfer is complete.  When the transfer is very large though, the upload transfer proceeds and the XHR does not abort.  If the server sends the "Connection: close" header in the response, the XHR always aborts, but never shows the response code or status sent by the server.
Comment 1 Alexey Proskuryakov 2012-02-01 10:49:12 PST 
Do you have a test case, or more specific steps to reproduce?

So far, this doesn't necessarily sound like a bug - it can be just that server and client notion of "transfer being complete" are naturally out of sync.
Comment 2 Craig Yoshioka 2012-02-01 14:18:55 PST 
I think you are right.  Checking through the XHR specs seems to indicate that this behaviour in Webkit is based on the spec.  I guess I'll to use WebSockets if I want to get the desired effect.