Step 1/2 for repairing mod_rewrite after the recent child spawning changes
(child_info *pinfo !!). This is the easier part: We just avoid fiddling with the pinfo stuff by using the reliable piped logs. Beside this repair reason its the preferred way, too. The previous code in mod_rewrite is from dates where no reliable piped logs exist ;-) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@81327 13f79535-47bb-0310-9956-ffa450edef68
Please register or sign in to comment