Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
first bad redirect is saved in browser
I created a 301 redirect on .htaccess file on linux shared server website
I did it incorrectly and have changed redirect to another website
But firefox browser windows 10 (my machine only: I did not try on other computers) still has first redirect.
I dont want to close browser or restart my windows 10 computer
I did it incorrectly and have changed redirect to another website
But firefox browser windows 10 (my machine only: I did not try on other computers) still has first redirect.
I dont want to close browser or restart my windows 10 computer
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Flush the cache manually under Tools, Options, Advanced, Network, Cached Web Content.
If that doesn't resolve it then you'll need to restart Firefox.
If that doesn't resolve it then you'll need to restart Firefox.
Good rule of thumb. Always start with 302s (not cached in browser) first, till you've debugged everything correctly.
To fix your problem, I'd first suggest you visit your page using a non-browser tool, like curl to ensure you've actually fixed the problem at the server level. You'll do this via...
Which will generate the entire redirect chain related to the URL provided to curl.
Can't tell you how many times I've spent a good bit of time chasing a redirect problem, then to realize the 301 was cached on the server side + still serving.
You can also just post your URL here + someone can test it for you, to ensure you've broken the 301 redirect chain correctly at your server side.
To fix your problem, I'd first suggest you visit your page using a non-browser tool, like curl to ensure you've actually fixed the problem at the server level. You'll do this via...
curl -I -L URL
Which will generate the entire redirect chain related to the URL provided to curl.
Can't tell you how many times I've spent a good bit of time chasing a redirect problem, then to realize the 301 was cached on the server side + still serving.
You can also just post your URL here + someone can test it for you, to ensure you've broken the 301 redirect chain correctly at your server side.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial