Forum Moderators: phranque

Message Too Old, No Replies

Suggestions for ways to test redirects

         

laurenji

5:41 pm on Apr 2, 2015 (gmt 0)

10+ Year Member



Hello everyone,

I am looking for a way to test .htaccess files and redirects before placing them live on a website. Previously, I had done this by having a domain set up as a "tester" domain on an Apache server, writing all redirects as if they applied to that URL, and testing them to see if they worked the way I intended. After I was satisfied they worked, I made any necessary domain substitutions (not usually necessary), and put the .htaccess file on the actual domain instead.

For various reasons, I don't have access to that set up any more. My first response was to say that we should buy a domain with company money (as opposed to my personal money), and host it on our company servers. Basically, recreating the same setup with company funds.

However, before we do that, my supervisor asked me to look into whether there were any other tools that could be used to do similar things and I was wondering if you all knew of any? Or is setting up an "empty" domain the best way to do it?

Would appreciate the help.

phranque

7:01 pm on Apr 2, 2015 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



i would strongly suggest configuring one or more subdomains to use for developing, testing and staging your changes without affecting your live server.

these subdomains should be blocked from unwanted visitors using HTTP Basic Authentication or something similar.

lucy24

9:32 pm on Apr 2, 2015 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



For various reasons, I don't have access to that set up any more. My first response was to say that we should buy a domain with company money (as opposed to my personal money), and host it on our company servers. Basically, recreating the same setup with company funds.

If your company can't afford the $10 or so per year it costs to register an unwanted name, I sincerely hope your resumé is up-to-date.

In addition to maintaining a test site on your "real" server, you can set up a pseudo-server like MAMP or WAMP or XX-whatever-it-is to run off the nearest available computer. Just remember to change the name in all the targets! (I just use leading / with [R=301] flag instead of saying explicitly domainname.local or whatever I'm testing at the moment. Since it's just me, I am not particularly worried about domain name canonicalization ;) )