3 ms·
Actually using HTTP 1xx will trigger hideous bugs, and worse those bugs will be timing-dependent. There is exactly one (non-websocket, which isn't really HTTP j
by yencabulator 6y ago
Actually using HTTP 1xx will trigger hideous bugs, and worse those bugs will be timing-dependent. There is exactly one (non-websocket, which isn't really HTTP just pretends to be) codepath used in the wild: preapproval for a large file upload.
This problem is one reason why success/error should NOT be the first thing to send. It should be a trailer.
(HTTP/HTML tendency to substitute the response body for a human-visible error would require another mechanism to "reset" the response body.)
- ArchOversight 6y ago> codepath used in the wild: preapproval for a large file upload There is no current browser, or client that by default will send an Expect: 100-Continue. cURL removed it because it was too often broken. See https://curl.se/mail/lib-2017-07/0013.html https://curl.se/mail/lib-2017-07/0013.html As of right now, while server authors will continue to need to support it, it is unlikely that it is a well tested code path, and it will likely break in weird ways even trying to use it. So pre-approval for a large file upload is not even valid anymore.
- yencabulator 6y agoAlright, make that the only codepath ever used in the wild. Even more reason to avoid 1xx.