At 12:27 PM 7/16/99 , Henrik Nordstrom wrote:
>Jon Drukman wrote:
>
>> 206.169.18.74 - - [15/Jul/1999:16:33:58 -0700] "GET
>> http://hudsucker.gamespot.com/shared/vote_now.gif HTTP/1.0" 304 259
>> TCP_MISS:DIRECT
>
>
>Problem is that Squid has not seen the whole object and thus it hasn't
>been cached. The above is only a reply to a If-Modified-Since request
>(HTTP status 304, Not Modified), and such replies are not cached by
>Squid at this time.
But it does get the whole object at least once. Look:
206.169.18.74 - - [16/Jul/1999:13:19:28 -0700] "GET
http://hudsucker.gamespot.com/shared/poll_yesbar.gif HTTP/1.0" 200 409
TCP_MISS:DIRECT
206.169.18.74 - - [16/Jul/1999:13:19:33 -0700] "GET
http://hudsucker.gamespot.com/shared/poll_yesbar.gif HTTP/1.0" 304 259
TCP_MISS:DIRECT
206.169.18.74 - - [16/Jul/1999:13:19:34 -0700] "GET
http://hudsucker.gamespot.com/shared/poll_yesbar.gif HTTP/1.0" 304 259
TCP_MISS:DIRECT
206.169.18.74 - - [16/Jul/1999:13:19:35 -0700] "GET
http://hudsucker.gamespot.com/shared/poll_yesbar.gif HTTP/1.0" 304 259
TCP_MISS:DIRECT
the first line shows a 200 status code. why does it keep checking in the
subsequent requests instead of serving the cached version?
Jon Drukman
Director Of Technology
GameSpot
Received on Fri Jul 16 1999 - 14:02:37 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:47:26 MST