- From: Rodger Combs <rodger@plexapp.com>
- Date: Thu, 19 Feb 2015 02:22:33 +0000
- To: ietf-http-wg@w3.org
It appears that the current HTTP/2 spec doesn't allow 206 Partial Content replies to be of indeterminate length. RFC 7233 section 4.2 requires that the "last-byte-pos" field in the Content-Range header be a number, rather than "*". It'd be convenient to allow the last byte position to be indeterminate if the requested range lacked a "last-byte-pos" field. Would this change be within the scope of HTTP/2 to make? Thanks, --Rodger Combs
Received on Wednesday, 4 March 2015 19:12:21 UTC