Dear IETF: Are you fucking kidding me?
To get an RFC .txt file I must allow Cloudflare and Google tracking?
Are you serious? This is wrong on all OSI layers!
@MacLemon CloudFlare everywhere!
@lanodan Thanks for sharing. I do have my local RFC backup as well. (Not really current though to be honest.)
Still… the IETF must not block users in any way. (“must not” to be interpreted as defined in RFC 2119.)
@TerrorBite Thanks for the update! :-D
@MacLemon works fine via tor 😉
@M0YNG That connection was via Tor.
@MacLemon hmm, I am using the tor browser, if that helps.
@jasper That was a request to a .txt file. So, nope, they cannot test for .js in that case. I mean, sure they *can* but it will fail 100% meaning it‘s a pretty useless test, not only in this case.
Either way, among many institutions on the internet, the IETF is probably one of the least in the position to cause any blockings caused by their contractors. Especially given their requirements for internet access at IETF meetings it‘s really hard to understand why they‘d block anything.
FTR cloudflare sucks.. I am not really fishing for "reasons it makes sense for Cloudflare/IETF to do this".
@jasper The IETF does indeed serve text/plain on that URL. As expected, as they should.
Cloudflare does the MITM attack here by messing with everything they can for no observable reason. And yes, of course uMatrix blocks 3rd party frames/.js. It‘s obviously for a good reason to do so.
I understand what‘s going on here, I‘m just not willing to accept that shit, especially from the IETF.
@utzer I'd rather gopher that file. I really hate Email.
But you're right, I should drop them a note of that problem.
@utzer I would be quite astonished if they weren't aware of the problem at all. But just maybe their ops are less considerate than other IETF people. Not impossible, just very unlikely.
Just tried. No cloudflare, no captcha, just txt (also html). Both Torbrowser and direct without any extra allowance in uMatrix and nothing blocked. No other domain.
Ah true, https connects to 126.96.36.199 which is CLOUDFLARENET
dig www.ietf.org a
IN A 188.8.131.52
@MacLemon I just checked; ftp still works to that address.
(I think that is the only way I have ever read an rfc, to be honest. Well, no, I have read them via links - but always mirrored, I believe. I believe the only way I've gone to the ietf website was via ftp. Thus my concern: was my traditional method now not working? And, no, it still does.)
@laggard You may want to check to whose IPs that hostname resolves to…
@epi I don't mind them using a CDN, but I do mind them blocking legitimate requests via their CDN.
chaos.social – a Fediverse instance for & by the Chaos community