You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pretty sure that i've seen cases in the past where clearing a FireFox History & Filecache didn't also remove cached 301 redirects. (While of course that doesn't have to be the case with FFs current behaviour any more.) Maybe that's an interesting target for you?
The text was updated successfully, but these errors were encountered:
Ahh, very interesting! I wonder where the best place to store the identifier would be, maybe in a hashtag in the URL, eg fwd.from -> fwd.to/url#hash, and fwd.to/url#hash could be a single hosted page that sends back the hash/ID via a postMessage eventListener.
My first idea would be something like an iframe or AJAX-Request to a php file on the same host, which redirects to itself, just with changed query parameters ala test.php 301 -> test.php?foo=bar. But hashes might totally work, who knows ;)
(Sorry to say that i won't have time for Tests and Pull requests in this direction, but i wanted to write this idea down anyway.)
I'm pretty sure that i've seen cases in the past where clearing a FireFox History & Filecache didn't also remove cached 301 redirects. (While of course that doesn't have to be the case with FFs current behaviour any more.) Maybe that's an interesting target for you?
The text was updated successfully, but these errors were encountered: