6 ms·
You can see this on a lot of sites right now. You get the Akamai style error with something like: Reference: #11.453a2f17.1393u44848484.3aee33433 At the bo
by tyingq 5y ago
You can see this on a lot of sites right now. You get the Akamai style error with something like:
Reference: #11.453a2f17.1393u44848484.3aee33433
At the bottom of a very bland looking error page.
- lowbloodsugar 5y agoWhat's frustrating is that DNS is returning an address, instead of just failing, and so macos is caching that value (though it might be cloudflare doing that).
- space_ghost 5y agoWildcard DNS should be a prosecutable crime, punishable by no less than 20 years of hard labor. (Edit: Probably should have made it clear that this was a joke)
- breakingcups 5y agoI don't see how wildcard DNS is related to this? Nor how it's bad?
- gokhan 5y agoWildcard DNS helps me to handle multitenancy easily. What's wrong with it?
- dylan604 5y agoWhen did congress members start posting to HN?
- adamdoran 5y agoPresumably you're referring to the practice of answering queries for nonexistent records with an A record belonging to an advertisement page? (instead of doing the right thing answering NXDOMAIN, presuming no records of another type also exist for the queried name.) dnsmasq has a really useful feature for dealing with this: --bogus-nxdomain
- LeoPanthera 5y agoTo empty the macOS DNS cache: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
- halfmatthalfcat 5y agoYou could argue Akamai is the blandest of the CDN bunch; their UIs are atrocious.
- chrisweekly 5y agoTheir APIs are (or, were, last I suffered their use a few years ago) also terrible, eg blanket policy of refusing to cache any resource in the presence of "Vary" header, regardless of its value, and failure to honor standard HTTP headers... thankfully there are many other options for CDN, which are SO MUCH BETTER.
- youngtaff 5y agoSurely it depends what you vary on? Content-Encoding should be well supported, User-Agent less so and for very good reasons (there's too much variation in UA strings)
- judge2020 5y agohttps://learn.akamai.com/en-us/webhelp/adaptive-media-delivery/adaptive-media-delivery-implementation-guide/GUID-D7348F5A-D0B6-4753-88A7-05317F44F405.html https://learn.akamai.com/en-us/webhelp/adaptive-media-delive... > AMD automatically strips these headers out of requests to support caching for faster delivery. > I need the Vary HTTP headers: AMD can cache the associated object if the Vary HTTP header contains only "Accept-Encoding" and "Gzip" is present in the Content-Encoding header (AMD in this case standing for Akamai Media Delivery)
- acdha 5y agoIt wasn't that simple — IIRC, for a while Vary meant “don't cache anything, ever, under any circumstances” unless you made some custom configuration changes. Over time they _added_ support for just “Vary: Accept-Encoding” (IIRC less than a decade ago) and that was fragile. They improved that over time but it was painful for a number of years because there were various failure modes which meant things wouldn't be cached, or (IIRC) compression would be disabled for certain URLs sporadically if the first request for the option did not request transfer compression.