[users@httpd] 304 Status in access_log---Urgent

["PINNI, BALANAND (SBCSI)" <bp...@sbc.com>]

 All-

I am struggling on this issue for about 4 months .Please help me to
understand the situation.

Its IBM HTTP Server 2.0.42.1 and AIX 5.1 . Plus Websphere 5.0.

My question is I have set expiration for 24hrs on Client Browser Cache
as all files that are been accessed .That is ExpiresDefault A86400.

This is what is happening .After 24 Hrs i.e. after cache time gets
expired , same persons hits two URLS one in San Diego and the other in
Fairfield . We see mixed results as the file being accessed  was
modified 24 before the access time.

In case one we got updated file with 200 status in access_log , where as
for the other we got 304 status . That HTTP server is interpreting that
Cache time has not yet expired .But we know since 24 hrs have passed it
has to expire.

Any Ideas as to why such mixed results? HTTP configurations are same in
both the cases.
Should we not see any 304 at all in access_log ?

I verified HTTP header it sends correct date on file that was last
modified.If we delete cache for the browser it works ok as there is no
cache file to validate. Access time and expire time are getting updated
in browser cache perfectly ok.

So , please help me if some one has found solution to this situation.

Thanks in advance.




Balanand Pinni
23-H-4
SBC Services Inc
OBC ,Stl MO
*   314-206-5911
* bp3965@momail.sbc.com
* 1- 800- 451- 6897



   

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org