> > 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. Correct. Ryan ______________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] --------------------------------------------------------------
- Re: cvs commit: httpd-2.0/modules/mappers mod_negot... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0/modules/mappers mod_... Ryan Bloom
- Re: cvs commit: httpd-2.0/modules/mappers mod_... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0/modules/mappers mod_... Roy T. Fielding
- Re: cvs commit: httpd-2.0/modules/mappers mod_... Jeff Trawick
- Re: cvs commit: httpd-2.0/modules/mappers ... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0/modules/mappers mod_... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0/modules/mappers ... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0/modules/mappers mod_... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0/modules/mappers ... Rodent of Unusual Size
- Re: cvs commit: httpd-2.0/modules/mapp... William A. Rowe, Jr.
- Re: cvs commit: httpd-2.0/modules/mappers mod_... Jeff Trawick
