Why did the web server send the file instead of 304 http: was not modified?

My browser sends the following request to the server:

Host: www.imprimante.be User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Accept: */* Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3 Accept-Encoding: gzip, deflate If-Modified-Since: Fri, 29 May 2015 14:22:44 GMT If-None-Match: "90-5173935ad3a1a-gzip" Referer: http://www.imprimante.be/premier-avis-gratuit/ Cookie: <hidden> Connection: keep-alive 

URL used http://www.imprimante.be/wp-content/themes/mch_imprimante/js/theme.min.js? (note: www.imprimante.be is not yet available through wlan)

And the server will send me a file with this http (http: http: // http: // http:

 Accept-Ranges: bytes Connection: Keep-Alive Content-Encoding: gzip Content-Length: 137 Content-Type: application/javascript Date: Wed, 03 Jun 2015 07:18:03 GMT Etag: "90-5173935ad3a1a-gzip" Keep-Alive: timeout=5, max=99 Last-Modified: Fri, 29 May 2015 14:22:44 GMT Server: Apache/2.4.10 (Debian) Vary: Accept-Encoding 

As you may have noticed ( Last-Modified: Fri, 29 May 2015 14:22:44 GMT ), the file has not been modified since the last request.

So I don’t understand why the answer is not status 304: not changed.

I would really like to know why caching these files (and some others) does not work as I expect.

+5
source share
1 answer
+5
source

All Articles