Re: RFC7233 Range Requests: Indeterminate lengths

On 2015-02-19 03:22, Rodger Combs wrote:
> 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?

No, it's not in scope for HTTP/2, because:

a) HTTP/2 is done

b) HTTP/2 can be considered an alternate wire format for HTTP; so this 
kind of change should apply to HTTP/1.1 as well

That being said, extensions like this can be discussed in separate 
specs, independently of the HTTP protocol version.

Best regards, Julian

Received on Wednesday, 4 March 2015 19:33:26 UTC