> It doesn't logically follow that just because the server has a <limit>
> directive with that method name, it necessarily implements that method.
There is no following to the logic -- it is a definition.
In Apache httpd, LIMITable == implemented.
The only time 501 is preferred is if the server as a whole, in its entirety,
has never heard of that method before and isn't willing to pass it to
the resource handler to find out if it is allowed. 501 is normally only
sent by proxy servers that have been configured to block unknown methods,
and by old/special-purpose servers that only support a fixed set of methods.
....Roy
- Re: Extraneous socket read? Bill Stoddard
- Re: Extraneous socket read? dean gaudet
- Re: Extraneous socket read? dean gaudet
- Re: Extraneous socket read? Brian Pane
- Re: Extraneous socket read? dean gaudet
- Re: Extraneous socket read? Brian Pane
- Re: Extraneous socket read? Brian Pane
- Limit directive and unimplemented methods Cody Sherr
- Re: Limit directive and unimplemented methods Roy T. Fielding
- Re: Limit directive and unimplemented methods Cody Sherr
- Re: Extraneous socket read? Roy T. Fielding
- Re: Extraneous socket read? Bill Stoddard
- Re: Extraneous socket read? Brian Pane
- [PATCH] Re: Extraneous socket read? Brian Pane
