---- Stuck! Substitution #1 works but the rest of the url disappears
blurped - 8:30 am on Sep 1, 2013 (gmt 0)
does the string e28099 occur in any other URLs (not under the target hostname)? If not, you can simply leave off the conditions.
Yes, the group that handled this site before did not have a proper redirect in place for an old domain name, resulting in duplicate content issues. Thank you for clarifying the conditions, I went ahead and removed them.
The form (.*)e28099 is always a bit iffy. Are there any real-life limits to what might come before "e28099"? Put them in the rule, and non-matching requests will be out of there all the sooner.
ok, will do
You need to pay close attention to the ordering of rules here, because you've got multiple scenarios:
Unless your name is jdMorgan, do not use the [N] flag. Instead, rearrange your rules: FIRST rule for requests containing both THEN two rules for requests containing one pattern or the other
ok, that makes sense
how did it get there? did your cat walk across the keyboard?
The CMS the site was on before auto-generated page titles. That little phrase was the replacement for an apostrophe. But I like the cat story better :)
Targets of RewriteRules don't need quotation marks.
cool, fixed that too
Thanks for your help! I'm going to tinker around with it a bit more. The Redirect 301 is what is currently in place for the rest of the site urls. They work fine, but it seems like they might be inefficient since there's no flag for it to stop searching. So naturally, this little phrase problem led me to the Rewrite rule.