Message-ID: <3780B1E0.7A073A78@Golux.Com>
Date: Mon, 05 Jul 1999 09:23:44 -0400
From: Rodent of Unusual Size <Ken.Coar@Golux.Com>
Organization: The Apache Group
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: A tech question about the OPTIONS method.
References: <19990705131958.A8963@tagore.wipinfo.soft.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org
Status: O

Jayaram A wrote:
> 
> 1. If I have a document </path/to/the/doc.html> where
>    </path/to/the> directory is enabled for PUT method, does the above
>    statement from HTTP/1.1 spec imply that the request
>         "OPTIONS </path/to/the/doc.html> HTTP/1.1"
>    should be responded with the "PUT" method as well in the "Allow:"
>    header from the server?

Yes, unless the specific document has had that method
disabled somehow.

> 2. Secondly, if a server supports methods other than GET, HEAD, OPTIONS
>    and TRACE, (say PUT) should the request
>         "OPTIONS * HTTP/1.1"
>    be responded with PUT method as well in the "Allow:" header from the
>    server?

Yes.

> I understood that Apache Server does neither of the above.
> As I understood from the code that the response form Apache is always
> "Allow: GET, HEAD, OPTIONS, TRACE" irrespective of other methods
> supported, I just wanted to confirm my understanding about it.

No, Apache doesn't always respond with that set.  It is
deficient in dealing with OPTIONS responses when it comes
to new methods (such as the WebDAV ones) and dynamic resources
(such as CGI scripts), but it's *mostly* correct.
-- 
#ken    P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Software Foundation  <http://www.apache.org/>
"Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>