- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 28 Feb 2008 17:03:05 +1100
- To: Brian Smith <brian@briansmith.org>
- Cc: "'HTTP Working Group'" <ietf-http-wg@w3.org>
Ah -- from Allow's definition: > The Allow header field MAY be provided with a PUT request to > recommend the methods to be supported by the new or modified > resource. The server is not required to support these methods and > SHOULD include an Allow header in the response giving the actual > supported methods. Question: is this implemented anywhere? WebDAV folks? On 28/02/2008, at 12:36 PM, Brian Smith wrote: > > Mark Nottingham wrote: > >> I'm not sure it's a good idea to specify >> that Allow applies to individual representations... > > This is exactly what I meant. Allow doesn't apply to individual > representations, it applies to the resource. Entity headers should > always be specific to the entity. > > - Brian > >> >> >> On 27/02/2008, at 12:04 PM, Brian Smith wrote: >> >>> >>> Currently, "Allow" is defined as an entity-header, not a respones- >>> header. Its definition says "The Allow entity-header field >> lists the >>> set of methods supported by the resource identified by the Request- >>> URI." That means that (a) "Allow" never applies to the response >>> entity, and (b) "Allow" applies to all variants at the Request-URI >>> (not to any specific representation), (c) it doesn't make >> sense in a >>> request header. Note the last sentence of the definition of >> response >>> header in part 2, section 6: "These header fields give information >>> about the server and about further access to the resource >> identified >>> by the Request-URI." >>> >>> PROPOSAL: Make "Allow" a response-header. remove the reference from >>> Part 3, Section 4.1 and add it to the BNF for >> response-header in Part >>> 2, Section 6. >>> >>> - Brian >>> >>> >> >> >> -- >> Mark Nottingham http://www.mnot.net/ >> >> > > -- Mark Nottingham http://www.mnot.net/
Received on Thursday, 28 February 2008 06:03:23 UTC