Feature Request/Cache 404 Errors

  • We just had a situation where a site was sent a large amount of traffic to an invalid URL.

    Unfortunately the system did not fare so well, since unlike legitimate traffic which can be wp-cached and wp-super-cached, 404s must go through the entire app layer and get generated dynamically. So it would be nice to have an option to cache (especially supercache) 404 errors for a specific period, assuming of course the proper 404 header could be sent (might be more problematic).

Viewing 2 replies - 1 through 2 (of 2 total)

  • There’s an “is_404()” check in wp-cache-phase2.php. If you remove that then the plugin should cache those pages.

    Thread Starter John Keegan

    (@jkeegan2)

    Yes, I tried that actually but it appears that when you do that the 404 page gets cached but the actual response header that gets sent out when the cached page is retrieved is 200…

    So it would be an acceptable temporary measure but not something I’d want to do permanently (i.e. send all my 404s with 200 response headers). It would be nice if that functionality was built in so that the 404s were actually returned with 404 response headers.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Feature Request/Cache 404 Errors’ is closed to new replies.