www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From field...@hyperreal.org
Subject Re: protocol/378: Wrong behavior on an OPTIONS request
Date Tue, 01 Jul 1997 23:41:16 GMT
Synopsis: Wrong behavior on an OPTIONS request

State-Changed-From-To: closed-analyzed
State-Changed-By: fielding
State-Changed-When: Tue Jul  1 16:41:14 PDT 1997

Planning ahead, there are a few aspects of our current support
for the OPTIONS method that need to be fixed.

1.(short term) The default OPTIONS handler fails to check
   for and read the request message body.  It needs to do
   so since future enhancements to OPTIONS will probably use
   the body to pass a query syntax of some sort.  The same
   comment applies for the TRACE handler.

2.(medium term) The URL handler needs to special-case "*"
   and prevent the auth routines from rejecting it with
   a 403 Forbidden message.

3.(long term) The API needs to be able to support the
   checking of OPTIONS without performing or handling the


Release-Changed-From-To: 1.2b7-1.2.0
Release-Changed-By: fielding
Release-Changed-When: Tue Jul  1 16:41:14 PDT 1997

View raw message