The subpattern ^/ requires at least one arbitrary character. In your case it’s probably that trailing slash You should better stick to one writing (either with or without trailing slash) and redirect th wrong writing to the proper, like: remove trailing slash RewriteRule ^(.*)/$ /$1 L,R=301 # add trailing slash RewriteCond %{REQUEST_FILENAME}! -f RewriteRule ^.
*^/$ /$0/ L,R=301.
The subpattern . ^/* requires at least one arbitrary character. In your case it’s probably that trailing slash.
You should better stick to one writing (either with or without trailing slash) and redirect th wrong writing to the proper, like: # remove trailing slash RewriteRule ^(.*)/$ /$1 L,R=301 # add trailing slash RewriteCond %{REQUEST_FILENAME}! -f RewriteRule ^. *^/$ /$0/ L,R=301.
– PHPLOVER Feb 22 at 16:35 @PHPLOVER: You should serve the right URLs in the first place. These rules are only to fix those URLs that are misspelled. – Gumbo Feb 22 at 16:37 Ok thanks I see what you mean, so basically change my urls to the new friendly ones in site without trailing slash and the only time apache will need to remove the / is if someone obviously includes it.
Thanks I understand now. – PHPLOVER Feb 22 at 16:41 Sorry I was also meant to ask; should I setup a permanent redirect in . Htaccess to friendly urls?
Reason why is in Google my site just uses like signup/register. Php and not sure if I should do a permanent redirect? I know how to do to them but thought I would ask.
Thanks – PHPLOVER Feb 22 at 16:44 @PHPLOVER: Yes, you should already serve the documents containing the “new†URLs. – Gumbo Feb 22 at 17:04.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.