Too Many “HTTP 304” Calls by WordPress

  • I request the response from a WordPress developer on this.

    There is an issue with a Website Hosting service that is complaining to me that my WordPress website is making too many HTTP 304 calls to their server while I am working to build the website. As a result, they have blocked my access to the website twice now and each time left the block on for 4 days at a time.

    According to the server access logs, on the highest day, WordPress with the paid theme and plugins, there were 14,393 HTTP 304 calls to the server. This was over 18 hrs of working the WordPress site (Long Day).

    What I would need is to speak to a WordPress developer about this issue so I can get some answers about WordPress. I do need some information to address this to determine of it is “normal” for WordPress to do make so many HTTP 304 calls or is it actually a problem, if a person works straight through for 18 hrs.

    I need information and confirmations to know how to approach this claim by the Website host.

    Thanks

    • This topic was modified 7 years, 11 months ago by mwarbinek. Reason: Added a tag
Viewing 5 replies - 1 through 5 (of 5 total)

  • HTTP 304 Responses are actually a good thing when done properly.

    Please check your plugins, your .htaccess file for lines other than the default rewrite rules, and check with your web host if the module mod_expires.c is installed and running on your server.

    I also advise not to develop using any manner of caching. Make sure you are getting 200 Responses until dev. is done, then enable caching.

    Thread Starter mwarbinek

    (@mwarbinek)

    Thanks for the reply. I have a few questions.

    1. Sometimes script code is written in unique ways and hard to recognize, at least for me, can you give an example of what can be written that is other than the default rewrite rules that should not be there?

    2.”mod_expires.c” – I suppose this file can only be accessed by the webhost on their server? (cannot find it via FTP)

    3. Caching, other than caching plugins (which I do not use at the moment), there is no direct Admin module access to any other caching done by WordPress or the theme or plugins. I suppose I would have to search the PHP or script files for caching scripts and deactivate them – or – was this meant only for caching plugins?

    — or do you specifically refer to caching done by the server itself?

    4. Why would caching need to be turned off? Wouldn’t that create more calls?

    5. So by your response, it appears that 14,000 plus HTTP 304 calls is normal during development? – I did a call count to find the some of the following,
    : HTTP 304’s > 14,391 (all lines in the access.txt for the highest day)
    : revslider > 896
    : nivo.slider.js > 139
    : .jpg > 2,030
    : .png > 1,447
    : .js > 6,292
    : .css > 4,808 (believe there were 2 or 3 “.css” entries in one line for some of the lines).
    All of these counts are files called by WordPress, its theme and plugins during the one 18hr day. So this is Normal?

    PS: I have some experience with servers and databases, but compared to some, still new at it. I would love any help provided. Thanks

    1. Start by having only the default WP rewrite rules: https://codex.www.ads-software.com/Using_Permalinks
    2. This is module installed by your host. Ask them about it. Here is the doc: https://httpd.apache.org/docs/current/mod/mod_expires.html
    3. Caching rules can be used in .htaccess (that is generally all a cache plugin does other than perhaps writing minified cached files). See 1.
    4. When you are in development, you want to make sure each step is what the site is doing and not the cache.
    5. Check the access logs – ask your host – it’s not out of reason to have that many – maybe others are hitting the site. Need to see the access logs to know.

    When you are done with dev., and have the site running well without cache, go ahead and use it for site performance, but test all site functionality when you do. It is proper to get a 304 response when a site vistitor has already visited the site and not cleared their cache. New users should get a 200. then start to gett 304’s for content downloaded already, like .js files and .css files and images etc.

    Thread Starter mwarbinek

    (@mwarbinek)

    That is fantastic. Thanks for the info.

    I see now that a “304” call is telling the browser to access its cached files, which is likely why it is called “not modified”. Really, why can’t they call it “cached” instead.

    If I understand what you are saying, it is better to get the server to respond to HTTP 200’s instead of 304’s while in Development mode. So let me ask.

    Why is it better?
    and…
    Are 200’s better regarding a server restriction of 10,000 calls per day? – or is that the same as 304’s in that context?

    Thanks.

    • This reply was modified 7 years, 11 months ago by mwarbinek. Reason: added questions
    • This reply was modified 7 years, 11 months ago by mwarbinek. Reason: added context
    • This reply was modified 7 years, 11 months ago by mwarbinek. Reason: grammer correction

    Why is it better?

    So the changes you make are are clear.

    Are 200’s better regarding a server restriction of 10,000 calls per day? – or is that the same as 304’s in that context?

    That is 10,000 times a day that some part of your site does not have to be sent by your server.

    The distinction between 200 and 304 is:

    200 = load from server
    304 = load from local cache (because you already downloaded that resource by visiting that site/page and it is sitting in the cache in your browser)

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Too Many “HTTP 304” Calls by WordPress’ is closed to new replies.