- From: <jg@w3.org>
- Date: Sat, 01 Jun 96 14:59:15 -0400
- To: "Roy T. Fielding" <fielding@liege.ICS.UCI.EDU>
- Cc: Paul Leach <paulle@microsoft.com>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
I just went and looked at Content-Range and Range, and think that Roy is right; I don't think we have any problems in the spec. Range currently specifies it can only be used with Get or conditional GET requests. And yes, Roy is right about Content-Range being the right way to do range puts. We have three choices: 1) Right now, the spec is silent, and it may be best to keep it that way. 2) We could put some verbiage in PUT to the effect that an error should be returned if the client does not understand range puts if we wanted. As PUT is not implemented in most servers, I don't know how much of a compatibility problem we'd have with those few that do... 3) We can explicitly forbid the use of Content-Range with PUT operations. What think you all? I don't have a strong feeling one way or the other. - Jim
Received on Saturday, 1 June 1996 12:04:07 UTC