2 ms·
Worked in iOS Safari but failed in iOS Chrome. So, this new "HTTP/1.1" feature broke my existing (old-)HTTP/1.1 chrome browser! If they had called it HTTP/1.2
by 0x0 12y ago
Worked in iOS Safari but failed in iOS Chrome.
So, this new "HTTP/1.1" feature broke my existing (old-)HTTP/1.1 chrome browser!
If they had called it HTTP/1.2 they could send a non-308 redirect to HTTP/1.1 clients and 308 to HTTP/1.2.
Instead, we now have servers and clients both speaking "HTTP/1.1" (whatever that is this week) not able to interoperate.
Poor job.
- dragonwriter 12y agoRFC 7238 with the 308 status code isn't part of HTTP/1.1 (even under the new revision, which is in RFCs 7230-7235), its an experimental extension that expressly notes that implementers must be aware that HTTP/1.1 clients not specifically written to that extension will fall back to the behavior for status code 300 when status code 308 is encountered, and that 308 should not be used where that behavior is not acceptable. (This is the standard mechanism for extensibility in response codes within the existing high-level groupings in HTTP/1.1.)