Still problems with cache.

[Toppy]

Hi,

On http://www.cbssports.com/nba/scoreboard, following any game by clicking some "GameTracker" link under the games, the images there get requested over and over, even when (I think) the default sidki config tags them as to set caching parameters, yet I see them same images getting requested over and over again.

Here's some part of the log window :

Code:

BlockList 288: in Exceptions-U, line 1156
GET 288 : User Keywords: .a_js.a_embed.a_flash.
GET 288 : Cache-Control killed: no-cache
GET 288 : Pragma no-cache stripped

+++GET 288+++
GET /images/basketball/nba/players/60x80/498313.jpg HTTP/1.1
Host: sports.cbsimg.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Referer: http://sports.cbsimg.net/
Connection: keep-alive
+++CLOSE 287+++
RESP 288 : Cache-Control replaced: max-age=85348           NOW: public, max-age=345600
RESP 288 : Expires killed: Thu, 15 Apr 2010 03:28:36 GMT

+++RESP 288+++
HTTP/1.1 200 OK
Last-Modified: Wed, 29 Oct 2008 18:30:32 GMT
Server: Apache
Accept-Ranges: bytes
Content-Length: 6129
X-Media: ws1838-fe.tm
Content-Type: image/jpeg; PrxMsg: Filter Image
Cache-Control: public, max-age=345600
Date: Wed, 14 Apr 2010 03:46:08 GMT
Connection: keep-alive
Match 288: Top All Mark: Start     04.07.11 (multi) [sd] (d.r)
Match 288: Top Sniff: Sel. File Types     09.07.04 [sd] (d.1)
Match 288: Protect: Sel. File Types     07.07.15 [sd] (d.r)
...
...
GET 308 : Cache-Control killed: no-cache
GET 308 : Pragma no-cache stripped

+++GET 308+++
GET /images/basketball/nba/players/60x80/498313.jpg HTTP/1.1
Host: sports.cbsimg.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Referer: http://sports.cbsimg.net/
Connection: keep-alive
RESP 308 : Cache-Control replaced. WAS: max-age=85191           NOW: public, max-age=345600
RESP 308 : Expires killed: Thu, 15 Apr 2010 03:29:34 GMT

+++RESP 308+++
HTTP/1.1 200 OK
Last-Modified: Wed, 29 Oct 2008 18:30:32 GMT
Server: Apache
Accept-Ranges: bytes
Content-Length: 6129
X-Media: ws1838-fe.tm
Content-Type: image/jpeg; PrxMsg: Filter Image
Cache-Control: public, max-age=345600
Date: Wed, 14 Apr 2010 03:49:43 GMT
Connection: keep-alive
Match 308: Top All Mark: Start     04.07.11 (multi) [sd] (d.r)
Match 308: Top Sniff: Sel. File Types     09.07.04 [sd] (d.1)
Match 308: Protect: Sel. File Types     07.07.15 [sd] (d.r)
+++CLOSE 308+++

Please, does anyone know why it keeps on requesting the same file every time, although (to my knowledge) sidki's config is configured to make them cached ?

[JJoe]

(Apr. 14, 2010 03:54 AM)Toppy Wrote:  Please, does anyone know why it keeps on requesting the same file every time, although (to my knowledge) sidki's config is configured to make them cached ?

Browser bug? Firefox does not always send the If-Modified-Since header or use the cached image.

I added "*$SET(0=i_cache:2.)" to Exceptions-U and then loaded the same image many times, consecutively. Each time the image was downloaded.

The If-Modified-Since header for the image was sent after I did a google search or about:cache and then requested the image.

https://bugzilla.mozilla.org/show_bug.cgi?id=205557

[JJoe]

(Apr. 14, 2010 04:17 PM)JJoe Wrote:  Browser bug? Firefox does not always send the If-Modified-Since header or use the cached image.

I added "*$SET(0=i_cache:2.)" to Exceptions-U and then loaded the same image many times, consecutively. Each time the image was downloaded.

The If-Modified-Since header for the image was sent after I did a google search or about:cache and then requested the image.

This may be the expected behaviour.
about:config shows my Firefox's "browser.cache.check_doc_frequency" set to 3.

http://kb.mozillazine.org/Browser.cache...._frequency Wrote:Possible values and their effects

0

Check for a new version of a page once per session (a session starts when the first application window opens and ends when the last application window closes).

1

Check for a new version every time a page is loaded.

2

Never check for a new version - always load the page from cache.

3

Check for a new version when the page is out of date. (Default)

The 'tricky' part is "when the page is out of date",
http://www.mozilla.org/projects/netlib/h...g-faq.html .
Note that this faq is from Oct. 9, 2002.

So to start,
type "about:config" in the url bar and go.
Eventually, you should get a screen with a "Filter" field.
Type "cache" in the "Filter" field.

Is,
"browser.cache.check_doc_frequency" set to 3.
"network.http.use-cache" set to true.
"browser.cache.disk.enable" set to true.
"browser.cache.memory.enable" set to true.