agneslesage - 6:20 am on Aug 19, 2010 (gmt 0)

Thanks Jim!

I rather keep with the first option (remove the strings), as otherwise this is getting to complicate for me.
I happen not to have cross content on this site... and I dont think the way campaigns go, there is a chance robots track it and find duplicate content, so it should not be too bad.

Now, I have another 1 or 2 issues which are related.
In fact, it may give trouble for more people applying the optimized instructions provided, so it is good for the record: it seems one of the above rule is causing problem in WP admin menu of the e-commerce plugin(for editing categories)
Here is the guilty section:


# Redirect direct client requests for URL-path /index.php to / and for /folder/index.php to /folder/
# Likewise for default.php direct requests in root or in folder,
# and force www and strip parameters at same time, to avoid duplicate content.
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /([^/]+/)*(index|default)\.(php|html?|asp)([?#][^\ ]*)?\ HTTP/
RewriteRule ^(([^/]+/)*)(index|default)\.(php|html?|asp)$ http://www.atable.com/$1? [R=301,L]


I see 3 options:

1> remove the whole rule
Unless it affect something else in the row of instructions? I dont think so. It is probably not a very indispensable rule...?

2> remove the question mark
as it seems to be the striping off the parameters that mess up the admin

RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /([^/]+/)*(index|default)\.(php|html?|asp)([?#][^\ ]*)?\ HTTP/
RewriteRule ^(([^/]+/)*)(index|default)\.(php|html?|asp)$ http://www.atable.com/$1 [R=301,L]

Dos this still make sense? I think so...
And that way I also solve my issue of Google campaigns tracking. Please confirm this is OK

3> change the condition
in order not to apply this rule in wp-admin directory
But this is something only an expert like you knows to do...!

+> Another issue:
This htaccess is now causing problems if I leave it on root of my local version of the site, as it puts "www.atable.com" on the above rule, as well as this one:


# Redirect requests for non-blank, non-canonical hostnames to canonical hostname
# do not remove the parameters in string, so skip the original final "?" on target URL
RewriteCond %{HTTP_HOST} !^(www\.atable\.com)?$
RewriteRule ^(.*)$ http://www.atable.com/$1 [R=301,L]


I wonder if there is a way to "relativize" them. (it is always source of problem to have absolute paths and different version to manage).