I'm slightly puzzled over the date warnings as they all seem to be correct. As the date changes appear to be different based on their location is it reasonable to assume the varnish reverse proxy doing something to alter the results? if so how is the time warning calculated as different to that shown in the header response?
redbot response The server's clock is 7 sec ahead. The server's clock is 20 sec ahead. The server's clock is 1 day 1 hr ahead. The server's clock is 6 hr 33 min ahead.
multiple warnings on the image files so click the 4th image link Date: Sat, 10 Apr 2010 13:37:07 GMT X-Varnish: 1977584744 1967571076 Age: 92796 Via: 1.1 varnish Connection: keep-alive
Varnish is sending an Age header and also re-writing the Date header to be the current time, instead of leaving it as the original time the message was created (as HTTP requires). As such, from the outside, it looks like there's clock skew happening.
> I'm slightly puzzled over the date warnings as they all seem to be > correct. As the date changes appear to be different based on their > location is it reasonable to assume the varnish reverse proxy doing > something to alter the results? if so how is the time warning > calculated as different to that shown in the header response?
> redbot response > The server's clock is 7 sec ahead. > The server's clock is 20 sec ahead. > The server's clock is 1 day 1 hr ahead. > The server's clock is 6 hr 33 min ahead.
> multiple warnings on the image files so > click the 4th image link > Date: Sat, 10 Apr 2010 13:37:07 GMT > X-Varnish: 1977584744 1967571076 > Age: 92796 > Via: 1.1 varnish > Connection: keep-alive
On 11 April 2010 00:45, Mark Nottingham <m...@mnot.net> wrote:
> Hi,
> Varnish is sending an Age header and also re-writing the Date header to be > the current time, instead of leaving it as the original time the message was > created (as HTTP requires). As such, from the outside, it looks like there's > clock skew happening.
OK, I thought that it was something like that, but couldn't entirely work it out without also seeing the config of creativecommons varnish. I am curious as to the difference in clock skew based on images between different locations, and not the html content.
> I'm slightly puzzled over the date warnings as they all seem to be > correct. As the date changes appear to be different based on their > location is it reasonable to assume the varnish reverse proxy doing > something to alter the results? if so how is the time warning > calculated as different to that shown in the header response?
> redbot response > The server's clock is 7 sec ahead. > The server's clock is 20 sec ahead. > The server's clock is 1 day 1 hr ahead. > The server's clock is 6 hr 33 min ahead.
> multiple warnings on the image files so > click the 4th image link > Date: Sat, 10 Apr 2010 13:37:07 GMT > X-Varnish: 1977584744 1967571076 > Age: 92796 > Via: 1.1 varnish > Connection: keep-alive