[squid-users] bluecoat proxying to squid

Hi

Anyone ever used a bluecoat sg device to proxy to a squid ? The bluecoat
is basically another caching proxy, we have configured as a reverse
proxy that is forwarding requests to a squid box, which is also a
reverse proxy forwarding requests to apache.

We are setting the "Cache-Control" header like this:

Cache-Control: max-age=300, public, s-maxage=300

Most requests this is fine, and both squid and the bluecoat honour the
header and expire the document after the age has reached 300. Some
documents on the bluecoat however are not and you end up with headers
like this:

HTTP/1.1 200 OK
Date: Mon, 11 Jun 2007 10:28:55 GMT
Server: Apache/1.3.37 (Unix)
Cache-Control: max-age=300, public, s-maxage=300
Last-Modified: Mon, 11 Jun 2007 00:11:47 GMT
ETag: "2d306d-2104-466c9343"
Accept-Ranges: bytes
Content-Type: application/x-javascript
X-Cache: HIT from squid
Via: 1.0 squid:80 (squid/2.6.STABLE2)
Content-length: 8452
Connection: close
Age: 7763

where the age is increasing and the document never gets refreshed. When
the bluecoat asks our web servers direct without going via squid this
doesn't happen, so it seems to be a problem with bluecoat->squid. Our
squid is correctly refreshing the documents after they expire.

Anyone have any experience of this ? What could be the problem ?

--
Michael