Why I am not seeing HTTP 304 response code in my Apache logs even though my webpages are sending them? I've checked this in Chrome console:

enter image description here

My goal is to see which browsers are successfully using ETag header which I am sending with every page. As I said, I can see that in Chrome but not in server logs. Now I suspect that maybe headers are not logged at all, but I have to ask you about this.


If you use the default logging configuration of Apache 2, HTTP 304 responses should be logged in access logs (and not in error logs).

Here is an anonymized example of what I have in my access.log (with the default logging configuration): - - [25/May/2020:20:49:45 +0200] "GET /image.png HTTP/1.1" 304 515 "http://www.example.com/index.html" "Mozilla/5.0 (Android 9; Mobile; rv:67.0) Gecko/67.0 Firefox/67.0"

| improve this answer | |
  • 1
    thanks, actually it showed in my logs too, it was due to a delay probably because my site is on the shared hosting. – Dejan Dozet May 26 at 14:35
  • @DejanDozet, Yes, for example, I have a shared hosting on which logs are delayed by about 5 min. – Éric May 26 at 15:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.