On 02/12/2013 04:51 PM, Amos Jeffries wrote: >> I have a bunch of static content with appropriate Expires headers, but >> the URL contains a "?serial=123456" where the serial number is dynamic. >> Is squid smart enough to ignore the fact that the URL looks like a >> dynamic request, > > It *is* a dynamic request. Look see ... the URL is constantly changing. The URL ONLY changes for logging purposes. The content being served is static. The serial number is ONLY preset so I can comb the logs and find who/when picked up a resource. >> and use the expire headers to see that it's indeed >> static/cacheable content? > > Expires is relative to the URL. So if the URL changed its a *new* object > (MISS) with new Expiry details. Get the picture? > > > see http://wiki.squid-cache.org/ConfigExamples/DynamicContent for teh > configuration directives to change for cachign these responses. If you > have a new install of Squid-3.1 or later the default settings will cache > them. > > However, once you have them cached, you will probably still see a lot of > MISS happening because the URL are changing. For best cache HIT rate you > need to look at why those serial exist at all in the URL. They are > breaking the cacheability for you and everyone else on the Internet. Do > you have control over the origin server generating those URLs? If you > could explain what the serial is for exactly perhapse we could point you > in the direction of fixing the object cacheability. -- Scott Baker - Canby Telcom System Administrator - RHCE - 503.266.8253
