Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1195 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[7.1] No cache hit/miss in HTTP headers anymore

Mateo
Part of our business is web development, and one of the more useful ways our devs could see whether something was coming from the proxy cache was to view the HTTP headers. In here Squid would add a line in here stating whether it was a cache hit or miss.

After upgrade to ASG 7.1, this cache hit/miss header is no longer there. Is there anyway of turning this on?

Thanks
Matt


This thread was automatically locked due to age.
  • 0
    I've noticed that also. It seems they have replaced it with "cached=". I think cached="0" means that it was 'not' from cache and cached="1" means that the object was retrieved from cache. HTH
  • 0 in reply to rcochran
    Is that in the HTTP log? I see that also, but nothing in the HTTP headers on the client. There used to be a header called X-Cache that showed a hit or miss.

    I'm using the Live HTTP Headers extension in Firefox, and can't see anything relating to cache hits.