- From: Roy T. Fielding <fielding@kiwi.ics.uci.edu>
- Date: Tue, 17 Nov 1998 18:35:05 -0800
- To: Henrik Frystyk Nielsen <frystyk@w3.org>
- Cc: Jeffrey Mogul <mogul@pa.dec.com>, http-wg@hplb.hpl.hp.com
I'm fine with Jeff's updated wording, though I think worrying about the cached entry corresponding to the new request method should be part of the definition of cachable rather than having to repeat the conditional in several places. In any case, these are just clarifying what the implementer should be able to figure out on their own. What does bother me is >and also with 5.1.1 > >Servers SHOULD return the status code 405 (Method Not Allowed) if the >method is known by the server but not allowed for the requested resource, >and 501 (Not Implemented) if the method is unrecognized or not implemented >by the server. which is a bug -- it should say An origin server SHOULD return the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the requested resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. ....Roy
Received on Tuesday, 17 November 1998 18:44:50 UTC