Can someone interpret this entry in my htaccess file into english so that I can understand?

[cathibanks]

Alright...I just sent the whole redirect portion of the htaccess file to WilliamKammer.

Thank you so much, everyone, for your help.

[WilliamKammer]

Alright... just give me a day or two since you don't have me on retainer

[cathibanks]

You got it.  

Again, thank you so much for taking a look.

[WilliamKammer]

Escaping characters isn't a big deal with newer version of Apache. No need for all those slashes, unless it's something more complex. From what I've seen, at least.

[Travis_Bailey]

Would like to hear the resolution, given my endorsement.

[TomVolpe]

Hi,

That line of htaccess says:

If the host is legacytravel.com OR www.legacytravel.com, then lets try this rule below.

One conditions will always be true since the htaccess is on your site. So they cancel each other out, and are not needed.

The rule says if the URI matches the regular expression '^carrollton-travel-agent$' then redirect (r=301) to the target URL and stop processing rules (L flag for last)

Your RewriteRule target doesn't need characters escaping because it is not a regular expression, just a URL to redirect to. You also don't need the quotes, they're useful for grouping arguments with spaces in them but that's not affecting it.

Really this rewriterule doesn't accomplish anything, it redirects /carrollton-travel-agent to /carrollton-travel-agent, forcing the www. no matter which version is accessed. But if that is what you're wishing to achieve then there's a much simpler solution:

RewriteCond %{HTTP_HOST} !^www.legacytravel.com$ [NC]

RewriteRule ^(.*)$ http://www.legacytravel.com/$1 [R=301,L]

Notice we only use the \backslash to escape characters in regex patterns, and not in our target URL. What that rule will do is redirect any visitor where the host is missing the www to the equivalent page with the preceding www.

Hope that helps.

[Travis_Bailey]

It doesn't force www in any instance. That's why I'm looking forward to the solution.

[WilliamKammer]

Sorry to disappoint, Travis. Nothing too complicated, looks like it was just a botched www cleanup. A good old:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^legacytravel.com [NC]
RewriteRule ^(.*)$ http://www.legacytravel.com/$1 [L,R=301]

Will do the trick.

[cathibanks]

Alright, so if I take out all of the other nonsense...and just put this in...will that just make it go from legacytravel.com to www.legacytravel.com?

and that's that?

[WilliamKammer]

Yep. Of course, as with any change, back the old rules up into a text file before making the move... just in case it explodes everything (but it won't). Just a precaution.

[cathibanks]

Hello, my old htaccess buddy!

Let's say, perhaps, that a person wanted to change her main company blog from www.legacytravel.com/ramblings to www.legacytravel.com/blog.

Of course, all of the traffic would need to be re-directed.  the htaccess currently says:

BEGIN WordPress

<ifmodule mod_rewrite.c="">RewriteEngine On
RewriteBase /ramblings/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /ramblings/index.php [L]</ifmodule>

END WordPress

Would it be appropriate / effective to add something there that directs everything in light of the renaming of that subfolder?

Again, thank you in advance.