4 ms·
Yes, it can screw up caches and return unexpected content. Inserting an ad where an error should be is detrimental because the implementation often break stand
by ballard 13y ago
Yes, it can screw up caches and return unexpected content.
Inserting an ad where an error should be is detrimental because the implementation often break standards endpoint and intermediate apps depend on (http code, DNS query answer/s). An app that was expecting just JSON now dies in some horrible (maybe silent or end-user confusing stacktrace) way.
- sdkmvx 13y ago> Yes, it can screw up caches and return unexpected content. Then the cache is broken. Obviously not getting a response is going to confuse things, but there is a way to send back REFUSED without giving a positive or negative answer. Take HN's authoritative DNS server and ask it for information on yahoo.com. $ dig @sue.ns.cloudflare.com. yahoo.com. ... ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 28595 ... They are perfectly right to refuse service to non-customers, but I think it's bad network practice (legally right or not) to return incorrect information.