The tool returned:>>> http://abc.com
> ------------------------------
--------------
> 200 OK
> --------------------------------------------
Status: 200 OK Code: 200 Date: Sat, 08 Jul 2017 16:10:12 GMT Server: Apache/2.4.18 (Ubuntu) Last-Modified: Tue, 09 May 2017 01:03:45 GMT ETag: "1748-54f0ced6b7e40" Accept-Ranges: bytes Content-Length: 5960 Vary: Accept-Encoding Connection: close Content-Type: text/html On Sat, Jul 8, 2017 at 9:44 AM, Mitchell Krog Photography <mitchellkrog@xxxxxxxxx> wrote:I agree use this tool - http://www.redirect-checker.org/index.php It’s one of the best and doesn’t cache anything so any updates you make when working with redirects are picked up instantly.
Kind RegardsMitchell
From: Nick Kew <niq@xxxxxxxxxx>
Reply: users@xxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxx>
Date: 08 July 2017 at 4:43:01 PM
To: users@xxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxx>
Subject: Re: Problem with Redirect
On Sat, 2017-07-08 at 08:35 -0500, Blake McBride wrote:
> When, through my browser, I go to abc.com,
Probably what Eric said. But is there history to this?
As in, trying different variants on your configuration?
If you have previously had a permanent (301) redirect
from abc.com, then what you see is likely to be your
browser (rightly) remembering it.
Solution: use a lower-level tool than a general-purpose
browser when testing any aspect of your server setup.
A commandline browser like lynx, or a tool like curl.
(There are also web developer toolkits for Big Browsers.
They would also do the job, but give you more scope for
getting confused and messing it up).
--
------------------------------------------------------------ ---------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx