Bug 166633
| Summary: | iOS browsers not correctly handling HTTP 204 response | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Gordon Murray <gordon.murray> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ap, kidniki100 |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 10 | ||
Gordon Murray
The easiest way to reproduce is via the site: http://httpstat.us/
When you click the link "204 No Content" on a desktop browser it is handled correctly, the browser does nothing to view as per HTTP spec.
On iOS the view is changed which is incorrect.
Happens on both Safari and Chrome on iOS
See old bug 60206 for more background to previous attempts to fix.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
What is the difference between this bug and bug 60206?
Gordon Murray
(In reply to comment #1)
> What is the difference between this bug and bug 60206?
The original bug was never fixed under iOS, so now making this version OS specific.
Does this require Apple to resolve in iOS or is this a WebKit bug?
Alexey Proskuryakov
The proposed fix in bug 60206 is cross platform, and it's in WebKit. Not sure if it's known why this works as expected on macOS.
*** This bug has been marked as a duplicate of bug 60206 ***
Tommy Vogt
I don't think this is a Webkit bug. Firefox on iOS has the exact same issue and it is Gecko based. This is an Apple bug it seems. I don't know what the browsers get from the OS but it seems to be telling them to actually render a blank page. I've tested this in every iOS browser and the same thing occurs, a blank page gets loaded.