httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 38642] mod_rewrite adds path info postfix after a substitution occured
Date Sat, 20 Dec 2008 02:04:55 GMT

--- Comment #24 from Eric Covener <>  2008-12-19 18:04:54 PST ---
(In reply to comment #23)
> In regards to clobbering PATH_INFO:
> From my experiments, it would seem that PATH_INFO is in fact "regenerated"
> after a mod_rewrite ruleset has been processed. I'm not quite sure at what
> stage this occurs, but this would mean that, at least, CGI scripts will not be
> affected by the change.

This is the core directory walk processing that happens shortly after the
rewritten URL is reinserted.

> So I say forget the flag and change default behaviour - documenting it clearly,
> of course.

I think that definitely doesn't fly for 2.2 because I think it's quite easy to
end up with a ruleset that works under

Changing the behavior between releases has complications too because you have
to then know where your htaccess is running.

Ultimately I'm just more comfortable A) not regressing anyone with a legacy
ruleset lurking out in htaccess and B) making the choice explicit in the rule
after consulting the doc.

> Apache will automatically clean up the old string when the request is done,
> right? (Just sanity checking here.)

yes, everything in the request_rec is allocated out of a short lived (lifetime
of a request) APR pool.

> Also, why not just use

thanks, corrected.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message