Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Apache 304 reply number: what does it mean? 1
- Thread starter SaltyDuke
- Start date
-
1
- #2
The 304 error is somewhat misleading. The Apache Webserver logs it as an error, but it's really this. Someone visits your site today, and tomorrow, they go back to your site. When they do, their local system connects with your server, and then the server tells the local machine that the
information (html files, images, etc) are already in the cache of that users system, and the information is shown from the cache rather than the server itself. Apache logs this as the 304 error because it hasn't been modified since the last time that the user has accessed that part of your site.
This error is probably the online "good" error a user could get because this means that they have been to your site previously and have returned.
If you wish to not have this error anymore, then include a server side include (SSI) on the most visited pages. This will ensure that the visitor receives an HTML page that is parsed, and it must be parsed by the server (not from cache), thus making your HTML pages come from the server all the time.
from:
I interpret this to mean that the user who generates the 304 'error' is a return visitor whose browser has cached the web page and not 'dumped' the cache files before accessing the page again. If your page has changed, the user will not see the changes because the browser cache will deliver what was there the last time that page was accessed.
information (html files, images, etc) are already in the cache of that users system, and the information is shown from the cache rather than the server itself. Apache logs this as the 304 error because it hasn't been modified since the last time that the user has accessed that part of your site.
This error is probably the online "good" error a user could get because this means that they have been to your site previously and have returned.
If you wish to not have this error anymore, then include a server side include (SSI) on the most visited pages. This will ensure that the visitor receives an HTML page that is parsed, and it must be parsed by the server (not from cache), thus making your HTML pages come from the server all the time.
from:
I interpret this to mean that the user who generates the 304 'error' is a return visitor whose browser has cached the web page and not 'dumped' the cache files before accessing the page again. If your page has changed, the user will not see the changes because the browser cache will deliver what was there the last time that page was accessed.
- Status
Similar threads
- Locked
- Question