www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wr...@apache.org
Subject Re: mod_proxy/10056: ap_os_is_path_absolute
Date Sat, 16 Mar 2002 23:36:20 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: ap_os_is_path_absolute

State-Changed-From-To: open-feedback
State-Changed-By: wrowe
State-Changed-When: Sat Mar 16 15:36:20 PST 2002
State-Changed-Why:
What modules are loaded?  What is the specific conf that
applies to this particular request?

It appears that a module has some nasty interaction with
dir_walk, but that code in the 1.3 branch is very stable.
What was the specific request, which handler died, and is
it possible to provide a stack trace?

It's quite possible this is related to the mod_proxy changes,
if I'm reading your comments correctly.  I've reclassed the
bug as such.
Category-Changed-From-To: os-linux-mod_proxy
Category-Changed-By: wrowe
Category-Changed-When: Sat Mar 16 15:36:20 PST 2002



Mime
View raw message