Re: Redirecting paths with extra slashes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 9 Dec 2007 11:06:31 -0500
"Eric Covener" <covener@xxxxxxxxx> wrote:

> On Dec 9, 2007 1:09 AM, Christian Lerrahn <lists@xxxxxxxxxxxx> wrote:
> 
> > RewriteRule (.*/)/+(.*) $1$2 [R=permanent,L]
> >
> > fixes almost all of my problems. The only problem that remains is
> > that the pattern doesn't match at the beginning of the path.
> 
> 
> Works for me in perl and httpd.  Try RewriteLog and looking at the
> HTTP request/response directly.

When I log the rewriting, I see that the URL ///foo/bar gets logged
as /foo/bar already. However, this is only the case for the rewrite
log. In the access.log, I will still see the URL as I entered it. That
might also explain why the leading slashes disappear if there is a
redirect due to a match somewhere else in the path. Still the question
remains, why there is a 'wrong' path in the rewrite log.

@Eric: As you say that this works for you, I assume that you get
redirected. What version of Apache do you use? I'm on 2.2.6.

While there are no practical problems with leading slashes, I'd still
like to get rid of them, too.

Cheers,
Christian

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux