- From: Mark Nottingham <mnot@mnot.net>
- Date: Sat, 2 Apr 2022 12:30:45 +1100
- To: Guoye Zhang <guoye_zhang@apple.com>
- Cc: Roy Fielding <fielding@gbiv.com>, Marius Kleidl <marius@transloadit.com>, ietf-http-wg@w3.org
> On 2 Apr 2022, at 6:30 am, Guoye Zhang <guoye_zhang@apple.com> wrote: > > Unfortunately, we’ve determined that 1xx response is too unreliable for critical information. Many middleboxes drop it, and most client frameworks do not expose it. Therefore we only use it for feature detection and none of the critical functionalities depend on it. That's something you should re-examine. When running over HTTPS and especially HTTP/2 (or /3), it's been found sufficiently reliable; e.g., see browsers' emerging deployments of 103 Early Hints. Cheers, -- Mark Nottingham https://www.mnot.net/
Received on Saturday, 2 April 2022 01:31:07 UTC