Re: [squid-users] Re: Sibling cache peer for a HTTPS reverse proxy

I was looking for Vary headers from the origin server. But none visible.

Instead I see

1) broken cacheability headers.
The Expires: header says (Date: + 360 days), and s-maxage says 360days
BUT ... Last-Modified says 1970. So Last-Modified + s-maxage is already
expired.
  NP: this is not breaking Squid which still (incorrectly) uses Expires
header in preference to s-maxage. But when we fix that bug this server
will start to MISS constantly.

2) Authorization: header from eclipse.
 Server-authenticated requests can receive cached content but require
revalidation to the server to confirm that the content is legit for this
user. The server is responding with a whole new response object (200)
where I would expect a 304.
 Does the matching "HTTP Server REQUEST" to the parent peer for the
eclipse transaction contain an If-Modified-Since and/or If-Match header?

Amos
Received on Mon Jul 28 2014 - 11:36:58 MDT