https://issues.apache.org/bugzilla/show_bug.cgi?id=38642
--- Comment #23 from Aleksander Budzynowski <[email protected]> 2008-12-19 17:29:18 PST --- 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. The only place I can think of that will be affected is RewriteRules and RewriteConds that use %{PATH_INFO} themselves. But I would say they are relying on undocumented behaviour - in any ruleset that allows more than one substitution to occur, the URL goes through a "partial" state and what PATH_INFO should contain at that point isn't really stated anywhere. So I say forget the flag and change default behaviour - documenting it clearly, of course. If someone really wants to preserve PATH_INFO, they can use the env= flag to store it in another variable before making any substitutions. In terms of the code itself: > r->path_info = "\0"; Apache will automatically clean up the old string when the request is done, right? (Just sanity checking here.) Also, why not just use r->path_info = NULL; ? All the rest of the mod_rewrite code supports this. If you have a good reason not to use NULL, then you could just use this: r->path_info = ""; -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
