mod_rewrite/2925: Multiple // not collapsed for you by mod_rewrite

[Jay Soffian <ja...@cimedia.com>]

>Number:         2925
>Category:       mod_rewrite
>Synopsis:       Multiple // not collapsed for you by mod_rewrite
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Aug 29 16:10:00 PDT 1998
>Last-Modified:
>Originator:     jay@cimedia.com
>Organization:
apache
>Release:        1.2.6 (possibly 1.3.x)
>Environment:
Any
>Description:
If you have a RewriteRule such as:

RewriteRule ^/foo/bar /foo/baz [R]

This will not match URL's such as http://somehost/foo//bar

Obviously this can be taken care of by modifying the RewriteRule to

RewriteRule ^/+foo/+bar /foo/baz [R]

However, shouldn't mod_rewrite take care of this for you? If you use
the Redirect directive from mod_alias, the multiple slashes are collapsed:
            /* any number of '/' in the alias matches any number in
             * the supplied URI, but there must be at least one...

It looks like all mod_rewrite has to do is call no2slash at the
beginning of hook_uri2file. 

This is probably only wanted when the rule is a redirect rule.
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]