httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <field...@kiwi.ics.uci.edu>
Subject Re: 200 OK for an OPTIONS on a nonexistent URI?
Date Tue, 20 Apr 1999 22:58:52 GMT
In message <371CFC21.653F7DD1@Golux.Com>, Rodent of Unusual Size writes:
>I just noticed during some testing that 1.3.7-dev (at least all
>the way back to 1.3.5-dev) responds to an OPTIONS request for a
>nonexistent URI with "200 OK".
>
>Section 9.2 (OPTIONS) of draft 6 of the new HTTP/1.1 spec doesn't
>say anything in particular about whether this is appropriate; it
>just says that IF the response status is 200, then the response
>should include certain things.
>
>I'm inclined to think this should be returning a 404 Not Found for
>this..

The client might be trying to find out the options for a future PUT
request on that resource (that may not exist yet).  I wouldn't sweat
this one, at least not until something like mod_dav has a use for it.

....Roy

Mime
View raw message