On 02/13/2013 11:48 AM, Dave Dykstra wrote:
> Scott,
>
> If it's just for logging purposes, it would be better to use an http
> header such as User-Agent rather than putting it in the URL. It is part
> of the http standard to use the whole URL as a caching index.
Good point... I can send a head
On 2/13/2013 5:59 PM, Scott Baker wrote:
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.
Still the url is constantly changing and the proxy cannot know about any
of the
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
On 13/02/2013 10:48 a.m., Scott Baker 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 reque
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, and use the expire headers to see that it's indeed
static/cacheable cont
