[Webkit-unassigned] [Bug 10638] XMLHttpRequest on Windows doesn't give correct status

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Sun Sep 3 13:19:28 PDT 2006


http://bugzilla.opendarwin.org/show_bug.cgi?id=10638


daniel at brightbyte.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel at brightbyte.de




------- Comment #1 from daniel at brightbyte.de  2006-09-03 13:19 PDT -------
I can confirm that this appears to be a problem for some people (I don't have
Safari around to check for myself, so the below is second hand). This bug hits
safari users when using an extension i recently contributed to wikipedia - see
<http://bugzilla.wikimedia.org/show_bug.cgi?id=7219>. Note that I will try to
write a workaround, so it may not be possible to reproduce the problem on
wikipedia.

The Problem: apperently, status, statusText, responseText and maybe other
fields are null if the response from the server was empty. But empty content is
valid in HTTP - so responseText should be an empty string, and status and
statusText should represent what the server actually sent (200 OK, hopefully).

I have seen reports of the same problem showing up if the server responds with
"304 Not Modified" (see
<http://www.bitterpill.org/bp/2005-06/safari-xmlhttprequest-undefine.html>) -
please check this while you are at it. As per the w3c draft, 304s should be
handeled transparently by XMLHttpRequest (as 200 OK), unless If-Modified-Since
was sent explicitely using setRequestHeader, in which case the actual response
(with code 304) should be passed on the to JS code.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list