[Webkit-unassigned] [Bug 3810] Less common HTTP status codes cause the code to appear as undefined
bugzilla-daemon at opendarwin.org
bugzilla-daemon at opendarwin.org
Thu Jan 5 06:45:26 PST 2006
http://bugzilla.opendarwin.org/show_bug.cgi?id=3810
ap at nypop.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|New Bugs |XML DOM
------- Additional Comments From ap at nypop.com 2006-01-05 06:45 -------
With ToT, I cannot reproduce this for 200, 204 or 205 (perhaps, as a side effect of the fix in bug 5924).
The behavior is still largely different, though.
Basically, it seems that Firefox ignores the meaning of many HTTP statuses here (e.g. it still receives the
response data for 204 No Content or 304 Not Modified responses). OTOH, NSURLConnection doesn't pass
the data for 204, and emits an error for 304 - which may be correct.
Are there any cases that should be considered bugs left? Do we need to match Firefox exactly?
--
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