W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013


From: Alex Rousskov <rousskov@measurement-factory.com>
Date: Tue, 30 Apr 2013 19:18:49 -0600
Message-ID: <51806D79.6030002@measurement-factory.com>
To: IETF HTTP WG <ietf-http-wg@w3.org>

    These comments are based on the "latest" snapshot dated Mon 29 Apr
2013 03:13:05 PM MDT at

I hope these comments are "editorial in nature".

> Clients MUST NOT use an entity-tag marked as weak in an If-Range
> field value and MUST NOT use a Last-Modified date ...

Please replace "use" with "generate" to explicitly exclude proxies from
policing these headers (i.e., to allow proxies to forward these headers
"as is"). This was already done for other If-Range header rules, but
these two MUST NOTs have slipped through the cracks.

> A client that cannot process a multipart/byteranges response MUST NOT
> ask for multiple ranges in a single request.

A similar concern here for "MUST NOT ask". Please reword the above to
use "MUST NOT generate".

This is especially important because a proxy may not be able to fully
"process" a multipart/byteranges response (whatever that means) but it
can still forward a request for multiple ranges and correctly forward
the 206 response back to the client because HTTPbis no longer allows
multipart/byteranges media type to determine the message body length.

> 4.1 206 Partial Content

Since HTTPbis no longer allows multipart/byteranges media type to
determine the message body length, perhaps it would be a good idea to
explicitly mention that a server MAY generate a 206 Partial Content
response (with single or multiple ranges) without a Content-Length
header and may use chunked encoding? I bet many clients will break when
this starts happening, and there are currently no examples or warnings
that would prepare developers for that possibility.

Thank you,

Received on Wednesday, 1 May 2013 01:19:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:10 UTC