www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject Re: mod_cgi/4490: mod_cgi prevents handling of OPTIONS requests
Date Wed, 02 Jun 1999 13:57:18 GMT
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

Synopsis: mod_cgi prevents handling of OPTIONS requests

State-Changed-From-To: open-suspended
State-Changed-By: coar
State-Changed-When: Wed Jun  2 06:57:12 PDT 1999

As the comment in the source remarks, very few CGI scripts
will respond correctly to an OPTIONS request.  The current
draft of the CGI/1.1 spec allows the server to intercept
this method (see <http://Web.Golux.Com/coar/CGI/>).  This
would have to be selectably controllable (i.e., would need
a directive to enable/disable it for specific scopes) to
keep unaware scripts from responding incorrectly.  I'm
marking this as suspended so it won't be forgotten, even
though it's on the list for the next major release cycle.

Severity-Changed-From-To: critical-non-critical
Severity-Changed-By: coar
Severity-Changed-When: Wed Jun  2 06:57:12 PDT 1999

View raw message