4 ms·
That's actually a really viable theory, especially given the "can't search for traceroute" thing - that spits out what seems to be a time-based error string.
by fredley 7y ago
That's actually a really viable theory, especially given the "can't search for traceroute" thing - that spits out what seems to be a time-based error string.
- ryanlol 7y agoIt’s not, that’s just standard akamai WAF behaviour. E: sorry, HN is throttling me and I can’t reply below. This is just a silly web application firewall that blocks a list of “suspicious strings”. There’s not much else to be said about it.