On Dec 9, 2007 1:09 AM, Christian Lerrahn [EMAIL PROTECTED] 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
On Sun, 9 Dec 2007 11:06:31 -0500
Eric Covener [EMAIL PROTECTED] wrote:
On Dec 9, 2007 1:09 AM, Christian Lerrahn [EMAIL PROTECTED] 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
On Fri, 7 Dec 2007 22:38:33 -0500
Joshua Slive [EMAIL PROTECTED] wrote:
On Dec 7, 2007 8:18 PM, Christian Lerrahn [EMAIL PROTECTED] wrote:
Hi,
I have a site that for some reason got indexed by Google with wrong
paths which contain too many slashes. E.g. instead of an entry for
/foo/bar
On Sat 08 Dec 2007, Christian Lerrahn wrote:
RewriteEngine On
RewriteRule (.*)//+(.*) $1$2 [R=permanent,L]
Thanks for that. I'm sorry to still bother. I'd like to get rid of
paths like //foo/bar, too, which do not match with this rule. To be
honest I don't quite understand the rule. That's
On Sat, 8 Dec 2007 15:40:09 +0100
Torsten Foertsch [EMAIL PROTECTED] wrote:
On Sat 08 Dec 2007, Christian Lerrahn wrote:
RewriteEngine On
RewriteRule (.*)//+(.*) $1$2 [R=permanent,L]
Thanks for that. I'm sorry to still bother. I'd like to get rid of
paths like //foo/bar, too, which
On Dec 7, 2007 8:18 PM, Christian Lerrahn [EMAIL PROTECTED] wrote:
Hi,
I have a site that for some reason got indexed by Google with wrong
paths which contain too many slashes. E.g. instead of an entry for
/foo/bar
there might be one for
/foo///bar
Now this is no problem for a Apache
Hi,
I have a site that for some reason got indexed by Google with wrong
paths which contain too many slashes. E.g. instead of an entry for
/foo/bar
there might be one for
/foo///bar
Now this is no problem for a Apache but it is for some of my pages
because they use relative paths. If I have an
