Mister Denial Posted August 8, 2014 Share Posted August 8, 2014 Hello everyone, I just noticed in Firefox network console that if I hit refresh on the page, it returns a bunch of 304 errors (see screenshot) - should that happen? On initial page load, no problem. On force full refresh, no problem. But regular refresh, ta da, a lot of 304 errors. Is this a server issue (VPS), or is this a PS configuration error? Because if I google the 304 code, the consensus is that a server should never return this code unless badly configured. So I am worried my server might be screwed up. Thanks for your input. Dan Link to comment Share on other sites More sharing options...
El Patron Posted August 8, 2014 Share Posted August 8, 2014 When a validation request is made, the server can either ignore the validation request and response with a normal 200 OK, or it can return 304 Not Modified to instruct the browser to use its cached copy. The 304 response can also include headers that update the expiration time of the cached document. I do not think this is classified as an error. Link to comment Share on other sites More sharing options...
Mister Denial Posted August 8, 2014 Author Share Posted August 8, 2014 Hi Fred, thanks for your reply. So the 304 is a normal behavior of Prestashop 1.6 when hitting refresh? Link to comment Share on other sites More sharing options...
El Patron Posted August 8, 2014 Share Posted August 8, 2014 my understanding this is 'by' browser behavior (http level) between browser cache and server. 1 Link to comment Share on other sites More sharing options...
Mister Denial Posted August 8, 2014 Author Share Posted August 8, 2014 Okay, I was checking in Firefox Network Console - on your own website, does it return the same results when you refresh it? Link to comment Share on other sites More sharing options...
Mister Denial Posted August 9, 2014 Author Share Posted August 9, 2014 Checking and comparing with other e-commerce websites, including Amazon, I come to the conclusion that this is indeed a normal behavior with Firefox. Like el Patron said, it seems to be linked to cache comparison between server and client browser. Link to comment Share on other sites More sharing options...
Recommended Posts