Content ranges in HTTP/1.1

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Larry Masinter: "Cache-control: proxy-maxage as MUST for HTTP/1.1?"
• Previous message: Misha Wolf: "Unicode Conference - March 1997 - Reminder"
• Next in thread: Koen Holtman: "Re: Content ranges in HTTP/1.1"
• Reply: Koen Holtman: "Re: Content ranges in HTTP/1.1"

For the HTTP/1.1 support of content ranges, what should be the correct =
server response for a byte range that is outside the actual contents of =
the file?

For example, suppose I have a file 1000 bytes in length, and the request =
sent to my server includes a range request of:

Range: bytes=3D2000-2500

What is the correct response?  Is a 204 the correct response?  Is a 206 =
with a Content-Length of 0 Correct?  If so, then what is the =
"Content-Range:" that one should return?

The HTTP/1.1 spec seems to imply that the right thing would be to return =
200 along with the entire content (as a general error handling =
mechanism), however in this case, doing so seems to be the worst =
response and defeat the purpose of using content ranges.

Thanks,

-Matt Bookman
<matt@pointcast.com>

• Next message: Larry Masinter: "Cache-control: proxy-maxage as MUST for HTTP/1.1?"
• Previous message: Misha Wolf: "Unicode Conference - March 1997 - Reminder"
• Next in thread: Koen Holtman: "Re: Content ranges in HTTP/1.1"
• Reply: Koen Holtman: "Re: Content ranges in HTTP/1.1"