Mediafire anonymisation and referer headers
![]() ![]() |
Hi dkitty, I saw your post regarding my fork of W.A.R. (which I ended up removing after you pushed your anonym.to update) but wanted to get back to you regarding referer headers and anonymisation. The main reason I forked WAR with explicit removal of referer headers was that Chrome(ium) does send the referer header when AJAX requests are made. As you noted in a changelog/discussion somewhere, certain sites have been monitoring referrers and taking down files linked from specific sites so making the checking process as anonymous as possible is important. I don't plan to re-fork W.A.R. but I think you'll agree that because of this behaviour in Chrome, it'd be a good idea to explicitly set referers to blank to avoid takedowns. I have also noticed that MF have started blocking anonym.to as a referrer so linkified URIs are still being blocked :( There are a lot of other options but may I suggest 'datab.ug/r/'? It's a script I hacked up in the wake of the referer blocking shenanigans and I am happy for it to be used as it will actually nullify the referer in most cases (instead of just setting it to some middleman URI like anonym.to). Query syntax is http://datab.ug/r/?[uri] and the URI needs to have a http(s):// at the moment (I need to change the query data handling). An example which will throw the received referer header is http://datab.ug/r/?http://httpreferrer.com/ Cheers,
|
![]() ![]() |
Thanks for the info! You're right, Chrome seems to be sending referers on AJAX requests. Will be solved with the next update. As for anonym.to, I'll think it over. It's kinda unbelievable they'd block content on such basis. :-) |
![]() ![]() |
Glad I could help :) I thought it was a bit crazy too as it seems like a simple referral site could not possibly violate the ToS in any meaningful way but they appear to be blocking requests via anonym.to consistently for me. Edit: I've had confirmation from a handful of other people that using anonym.to as a referrer resulted in being redirected to the error 385 page. The links I got them to test are:
|
![]() ![]() |
I see this as an issue too, mediafire adds recapcha if you enter with an anonym.to url, maybe could be better to change anonymizer to per site basis btw the script doesn't have the auto update url, have update by itself?
// @updateURL https://userscripts.org/scripts/source/101707.user.js |


