- From: Mark Nottingham <mnot@mnot.net>
- Date: Sun, 20 Jul 2014 14:59:10 -0400
- To: HTTP Working Group <ietf-http-wg@w3.org>
Roy’s point below hasn’t been discussed in the context of HTTP/2 before IIRC; he’s right in that the nature of expect/continue in HTTP/1 is not just hop-by-hop. Given that, it sounds like we need to address this issue (e.g., using Julian’s patch), and also adjust our existing text about 100-continue (and perhaps even about 101). That’s not to say that the WG can’t decide to deprecate further 1xx status codes in a separate document; just that HTTP/2 needs to carry this HTTP semantic (as per our charter). I’m going to mark this as editor-ready soon. Any further comments? Thanks, On 18 Jul 2014, at 1:19 pm, Roy T. Fielding <fielding@gbiv.com> wrote: > If we don't support 100 then we can't ask the endpoint (not just the > next hop) to verify that it will process the data in a large upload before > sending that large upload. I don't care if browsers don't use this feature. > It is commonly used in authoring environments for customers with large > data nodes (GIS and DAM). h2 framing can only do the same if there are > no intermediaries. -- Mark Nottingham http://www.mnot.net/
Received on Sunday, 20 July 2014 18:59:37 UTC