httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: cvs commit: httpd-2.0/modules/mappers mod_negotiation.c
Date Thu, 23 Aug 2001 21:14:49 GMT
From: "Ryan Bloom" <rbb@covalent.net>
Sent: Thursday, August 23, 2001 4:05 PM

> > Because I'm less than clear on the subject, so I will ask (now that you've
> > reminded me)...
> >
> > who's job is it to answer an M_OPTIONS request?  Every module's?  Then the
> > mod_cgi family is broken (this is what led me to discover that viewcvs.cgi
> > hangs on HEAD, maybe other cgi's are hanging, as well.)
> >
> > If it's the handler's, we should review all the modules for this
> > requirement. If it's supposed to be the server, this code can disappear.
> 
> Both should be able to handle it.  Basically, the default handler should do it
> if nobody else does.  But, modules should be allowed to handle M_OPTIONS
> requests.

So what you are saying, if I understand, is that a module _may_ handle M_OPTIONS,
but it _MUST_ return DECLINED if it doesn't want to deal with it, so the core
_WILL_ handle it.  Correct?

I don't think that's what we are doing everywhere, today.




Mime
View raw message