My 404 response are being cached by section.io by default, why is this?
One really easy way to attack a server is to send a huge number of requests for pages that do not exist. Although delivering a single 404 (Not Found) to a client is pretty light work for a server relative to requests for images and HTML documents, multiplying that by 100 or 1000 per second can significantly slow a server down or even cause it to crash. The section.io platform caches 404s by default to protect against this kind of attack. With 404 caching enabled, our proxy servers can deliver the cached 404s and your origin never even sees the barrage of requests.