W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2009

Re: GET/HEAD support "MUST"

From: William A. Rowe, Jr. <wrowe@rowe-clan.net>
Date: Thu, 29 Jan 2009 15:08:02 -0600
Message-ID: <49821AB2.4090004@rowe-clan.net>
To: Julian Reschke <julian.reschke@gmx.de>
CC: Geoffrey Sneddon <foolistbar@googlemail.com>, HTTP Working Group <ietf-http-wg@w3.org>

Julian Reschke wrote:
> 
> Geoffrey Sneddon wrote:
>>
>> Hi,
>>
>> Both RFC2616 and bis both include the following:
>>> The methods GET and HEAD MUST be supported by all general-purpose
>>> servers.
>>
>> This is unclear for several reasons:
>>
>> a) Although the server MUST support those two methods, MUST it support
>> it for every resource?
> 
> Dunno.

It must support them in tandem.  Implementing HEAD that corresponds to
anything except GET is not valid.  Implementing GET without HEAD is not
valid either.

Nothing says a resource must support them, however.  E.g. PUT to a specific
URI might be valid, but there is no resource yet before PUT, ergo GET and
HEAD would be 404 not found.

It's probably a good idea to implement them, in a write-only server they
could consistently return 404.
Received on Thursday, 29 January 2009 21:08:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:00 GMT