I thought this had been documented when I added the code. AcceptPathInfo on|off|default [core directive - defaults to, 'default']
AcceptPathInfo 'on' in any context will allow additional path info in all requests to that context [e.g. <files >, <location >, <directory > etc.] AcceptPathInfo 'default' disallows additional path info for the default handler [e.g. normal files] yet allows it for CGI requests. AcceptPathInfo 'off' also disallows additional path info for CGI requests. In general, one would choose AcceptPathInfo 'off' to prevent 'namespace polution' where thousands of potential URIs map to one resource. Where a cgi application uses the path info to select content (e.g. the viewcvs.cgi application) one would set AcceptPathInfo 'on', which allows CGIs and filtered content from the default handler to all accept path info. AcceptPathInfo 'default' should retain the Apache 1.3 behavior, allowing path info in CGIs and not in default requests. Note this behavior varied between vendors of Apache-derived products, some of whom (such as IBM WebSphere) allowed the default handler to accept path info. Hope this is a thorough enough dissection. If your results vary, we have a problem Houston, let me know what you observe. At 04:57 PM 3/25/2002, you wrote: >Can someone remind me how 2.0 is supposed to handle determining which >resources accept POSTs? Can you post to the default-handler (to give >input filters a crack at it)? > >---------- Forwarded message ---------- >Date: Mon, 25 Mar 2002 23:19:46 +0100 >From: "Roozemond, D.A." <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: Suspected BUG in latest CVS: POST gives 405 in SSL > >Hi all, > >I think I've found a bug in the latest CVS, but I'm not sure. I'm running >apache 2.0.34-dev on SuSE linux 7.2, kernel 2.4.4. Got it via anonymous CVS >this evening. I thought everything was running fine, but I found a strange >thing: > >I created a test.htm: > >if I use http://.../test.htm everything is fine, I just get the same page >when I click submit. However, when I use the ssl-module: >https://.../test.htm I get a 405 error: > The POST method is not allowed for the requested URL. > >(With previous versions of apache 2 (I've been running 2.0.33-dev for quite >a while) everything worked fine, even when using the secure connection). > >Pretty strange in my opinion, but maybe I just overlooked something? Or is >it a bug? >Any ideas on the why and how of this problem will be greatly appreciated! > >Included the configure-command I used. If you want/need any more technical >information: ask please. > >Regards, > >Dan Roozemond > > >---------------------- >./configure --prefix=/usr/local/apache2033 --enable-expires --enable-headers >--enable-usertrack --enable-info --enable-rewrite --enable-so --enable-ssl >--with-ssl > >--------------------------------------------------------------------- >The official User-To-User support forum of the Apache HTTP Server Project. >See <URL:http://httpd.apache.org/userslist.html> for more info. >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED]
