www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Henke <and...@schlund.de>
Subject mod_rewrite/6671: backreferences aren't being expanded for internal RewriteMaps
Date Fri, 13 Oct 2000 18:33:16 GMT

>Number:         6671
>Category:       mod_rewrite
>Synopsis:       backreferences aren't being expanded for internal RewriteMaps
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Oct 13 11:40:01 PDT 2000
>Originator:     anders@schlund.de
>Release:        1.3.14
Linux 2.2.17, gcc, plain Apache 1.3.14
We've written an own internal RewriteMap for mass virtual hosting set up as following:
RewriteMap ourmapping int:ourmap
RewriteRule (.*) ${ourmapping:$1}

Apache 1.3.9 correctly hands the (.*)'s value to the map,
Apache 1.3.14 hands over the given backreferences name '$1'.
RewriteMap test int:toupper
RewriteRule (.*) ${test:$1}

should rewrite every URL to its uppercase counterpart;
instead, Apache hands the $1 over to the internal RewriteMap,
which again outputs the $1. Apache takes the given $1 as its
new URL and gives a 404.
Fix it :-)
 [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!     ]

View raw message