On 17/04/2014 7:40 a.m., Eliezer Croitoru wrote:
> Hey Amos,
>
> I have a tiny question which I am not sure about the answer(related to
> the topic).
> What would happen in the case which we deny reply or request headers?
> Would squid look at the Vary (headers as an example) and decide if it's
>
Hey Amos,
I have a tiny question which I am not sure about the answer(related to
the topic).
What would happen in the case which we deny reply or request headers?
Would squid look at the Vary (headers as an example) and decide if it's
a "Vary" object or it would "see" the request or\and respon
Hi Nick,
could you add a section for the WU SHA1 patterns to our DB of useful
StoreID patterns please:
http://wiki.squid-cache.org/Features/StoreID/DB
Cheers
Amos
Hi Jasper
I have compiled 3.4 to provide the store_id functionality implemented
by Ellizer.
I have it running in a production heterogeneous environment.
I'm still checking for bugs, but seems to work well.
#squid.conf file for Squid Cache: Version 3.4.4
#compiled on Ubuntu with configure options:
On Tue, 2014-04-15 at 14:38 +0100, Nick Hill wrote:
> URLs with query strings have traditionally returned dynamic content.
> Consequently, http caches by default tend not to cache content when
> the URL has a query string.
>
> In recent years, notably Microsoft and indeed many others have adopte
> > On Tue, 2014-04-15 at 13:11 +0100, Nick Hill wrote:
> >> This may the the culprit
> >>
> >> hierarchy_stoplist cgi-bin ?
> >>
> >> I believe this will prevent caching of any URL containing a ?
> >>
> >
> > Should I remove the "?" and leave cgi-bin?
>
> You can remove the whole line quite saf
Hey,
It might be not understood but StoreID in squid 3.4.4 might help with that.
I noticed that you are using SLES which I do not have a build node for yet.
Since there are dynamic variables in the url it is hard to cache it.
Note that there are other options in the request and response that can
On 16/04/2014 1:17 a.m., Jasper Van Der Westhuizen wrote:
>
>
> On Tue, 2014-04-15 at 13:11 +0100, Nick Hill wrote:
>> This may the the culprit
>>
>> hierarchy_stoplist cgi-bin ?
>>
>> I believe this will prevent caching of any URL containing a ?
>>
>
> Should I remove the "?" and leave cgi-bin
URLs with query strings have traditionally returned dynamic content.
Consequently, http caches by default tend not to cache content when
the URL has a query string.
In recent years, notably Microsoft and indeed many others have adopted
a habit of putting query strings on static content.
This coul
On Tue, 2014-04-15 at 13:11 +0100, Nick Hill wrote:
> This may the the culprit
>
> hierarchy_stoplist cgi-bin ?
>
> I believe this will prevent caching of any URL containing a ?
>
Should I remove the "?" and leave cgi-bin?
Regards
Jasper
This may the the culprit
hierarchy_stoplist cgi-bin ?
I believe this will prevent caching of any URL containing a ?
On Tue, 2014-04-15 at 12:09 +0100, Nick Hill wrote:
> Hi Jaspar
>
> I use an expression like this, which will work on almost all Limux
> machines, Cygwin on windows and I expect Mac OSX or a terminal in
> Android so long as you have a version of grep similar to GNU grep.
>
> echo
> "http://cac
Hi Jaspar
I use an expression like this, which will work on almost all Limux
machines, Cygwin on windows and I expect Mac OSX or a terminal in
Android so long as you have a version of grep similar to GNU grep.
echo
"http://cache.pack.google.com/edgedl/chrome/win/34.0.1847.116_33.0.1750.154_chrom
> >
> > Hi Pieter
> >
> > No, that gives me an incorrect regular expression error.
>
> NP: regex has an implied .* prefix and suffix on patterns unless you use
> the ^ and $ endpoint anchors.
>
>
> What are the HTTP headers for these requests and replies?
> The 206 status indicates a Range r
On 14/04/2014 10:50 p.m., Jasper Van Der Westhuizen wrote:
>
>>> refresh_pattern -i pack.google.com/.*\.(exe|crx) 10080 80% 43200
>>> override-expire override-lastmod ignore-no-cache ignore-reload
>>> reload-into-ims ignore-private
>>>
>>> I see the following behavior in my logs. This is for the
> > refresh_pattern -i pack.google.com/.*\.(exe|crx) 10080 80% 43200
> > override-expire override-lastmod ignore-no-cache ignore-reload
> > reload-into-ims ignore-private
> >
> > I see the following behavior in my logs. This is for the same
> > client(source). Multiple entries, like it gets downl
On 14/04/2014 19:32, Jasper Van Der Westhuizen wrote:
Hi all
I'm trying to cache chrome updates, but I see it always fetches over and
over again.
I have the following refresh pattern in my config.
refresh_pattern -i pack.google.com/.*\.(exe|crx) 10080 80% 43200
override-expire override-lastmod
Hi all
I'm trying to cache chrome updates, but I see it always fetches over and
over again.
I have the following refresh pattern in my config.
refresh_pattern -i pack.google.com/.*\.(exe|crx) 10080 80% 43200
override-expire override-lastmod ignore-no-cache ignore-reload
reload-into-ims ignore-
18 matches
Mail list logo
