4 ms·
I've seen this error before from other sites and it seems to be generated by Akamai rather than the apple.com origin. Does anyone with Akamai experience know un
by jvolkman 11y ago
I've seen this error before from other sites and it seems to be generated by Akamai rather than the apple.com origin. Does anyone with Akamai experience know under what conditions this message would be returned? Did someone at apple accidentally ACL off the planet?
- stevecalifornia 11y agoThis happens when a company uses Akamai's security product and you violate the security policy in place. It's basically a WAF. The big issue is it takes 45 minutes for changes to propagate through Akamai's network. So, you make a mistake and it takes fix time + 45 minutes to resolve.
- veb 11y agoI posted my comment before to the wrong commenter, but: I'm interested in their References -- it looks like each hit is a new hash, so they store that so they can refer to it. I don't know much about this side of stuff so it'll be interesting to know why they do that, or what the upside is of doing it that way...
- kevan 11y agoAkamai does indeed give unique reference codes for errors like these. There's a management interface where you can look up more info on what happened for each code, but in my experience lookup time is proportional to the time since the error happened.