search

samyk / evercookie

Produces persistent, respawning "super" cookies in a browser, abusing over a dozen techniques. Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.
https://samy.pl/evercookie/
4.42k stars 663 forks source link

Feature suggestion: URL redirect cache #122

Open Abromeit opened 7 years ago

Abromeit commented 7 years ago

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?

samyk commented 7 years ago

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.

Abromeit commented 7 years ago

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.)

samyk commented 7 years ago

Cool, appreciate the idea