This is a completely random thing, but I figured somebody here might have an answer.
A nonprofit I’m part of has an old website. They configured it with a 3-4 second redirect to the new site. The old site is there, and it’s visible initially - but then it redirects to the new site.
They want to get at the data on the old site. Is there any nifty little tool or anything that can prevent those page header redirects from firing off?
No ssh, no sftp. It’s a meta http-equiv refresh, so JS isn’t involved. No ability to edit the redirect since accessing the admin requires the redirect not being there.
Is the redirect pointing to a URL or an ip address? If a URL try disabling DNS on your Mac and access the old site by its ip address. As long as the admin page doesn’t have a redirect it might work
Curl might actually work: “In curl’s tradition of only doing the basics unless you tell it differently, it does not follow HTTP redirects by default. Use the -L, --location option to tell it to do that.”
Curl is an interesting option - I’ll check into that for future purposes.
In the meantime, I actually found something.
In Firefox, in about:config, there’s a setting for “accessibility.blockautorefresh” that can be set to “true”. Disables the http-equiv redirect, so the site is completely navigable without worrying about it popping up the other site.
Leave it to Firefox to have a detailed config option for something like that.