httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: r->allowed ?
Date Thu, 29 Jan 1998 19:35:10 GMT
A handler must ensure that the request method is one that it is capable of
handling.  Generally modules should DECLINE any request methods they do
not handle.  Prior to aborting the handler like this the handler should
set r->allowed to the list of methods that it is willing to handle.  This
bitvector is used to construct the "Allow:" header required for OPTIONS
requests, and METHOD_NOT_ALLOWED and NOT_IMPLEMENTED status codes. 

Since the default_handler deals with OPTIONS, all modules can usually
decline to deal with OPTIONS. 

Since the default_handler will always handle a GET, a module which does
*not* implement GET should probably return METHOD_NOT_ALLOWED. 
Unfortunately this means that a Script GET handler can't be installed by
mod_actions.

How's that?

Dean

On Thu, 29 Jan 1998 rasmus@bellglobal.com wrote:

> > It's a bug in mod_include... and mod_info, mod_asis, and mod_autoindex. 
> 
> Ok, so apparently a whole lot of people don't know when to use it.  A
> short summary here of when and why to set r->allowed would be handy.
> 
> -Rasmus
> 


Mime
View raw message