Support » Plugin: W3 Total Cache » [Plugin: W3 Total Cache] HTTP/404 caching as HTTP/200

  • We are using enhanced disk caching with caching enabled on 404s. Caching the 404s takes a load off WordPress, which takes some time (more than 0.5 secs) to field 404s, and we assume that means some processing too, which is something we want to avoid.

    However, we have noticed that our set-up results in our custom 404 page being served up with status 200. This creates problems, because we wind up caching the “200” in the CDN.

    A look at the code suggests that basic disk caching is set up to report cached 404s as status 404, and it is only enhanced disk caching that sets it as a 200.

    Why does enhanced disk caching do this, and what do we lose by using basic disk caching instead?

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: W3 Total Cache] HTTP/404 caching as HTTP/200’ is closed to new replies.