Summary: | XMLHTTPRequest responses do not include the correct statusText | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Jan Lehnardt <jan> | ||||
Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Enhancement | ||||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Mac (Intel) | ||||||
OS: | OS X 10.6 | ||||||
Attachments: |
|
Description
Jan Lehnardt
2009-09-16 10:38:03 PDT
Created attachment 39654 [details]
implements the described issue.
I don't think it's helpful to fake response status text - the one case when web apps need to know it is when it's non-default, and this patch makes it more difficult to detect the broken WebKit behavior. *** This bug has been marked as a duplicate of bug 24572 *** Sorry for filing a duplicate. My search for "responseText" didn't show #24572 (https://bugs.webkit.org/buglist.cgi?quicksearch=responseText). I don't think I understand Alexey's reasoning. This is a bug that makes WebKit behave non RFC conform and I don't see a good reason to not fix it except "too many people depend on it". I understand that the open web is not the only target for WebKit users and that in some environments WebKit is the only engine to program against, but I believe the majority of users could do with the correct behaviour. Especially when it is only "wrong" on the Mac platform. I also don't think this is "faking" response codes, it is just adding the correct ones. This is definitely a bug that should be fixed, but we need support from NSHTTPURLResponse to do that. There is no such thing as "correct" status text - the server may well respond with "HTTP/1.1 500 Please reboot me", for example. |