RESOLVED DUPLICATE of bug 60206166633
iOS browsers not correctly handling HTTP 204 response 
https://bugs.webkit.org/show_bug.cgi?id=166633
Summary iOS browsers not correctly handling HTTP 204 response
Gordon Murray
Reported 2017-01-01 01:32:14 PST
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
Comment 1 2017-01-01 11:46:26 PST
What is the difference between this bug and bug 60206?
Gordon Murray
Comment 2 2017-01-01 13:25:51 PST
(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
Comment 3 2017-01-01 13:35:16 PST
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
Comment 4 2017-01-01 14:12:41 PST
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.
Note You need to log in before you can comment on or make changes to this bug.