On 06/21/2013 03:26 PM, Eliezer Croitoru wrote:
On 06/21/2013 02:45 PM, Daniele Segato wrote:
Hi,
is there a way to clear the cache without stopping / rebooting squid?
I usually stop squid, remove the caches from the filesystem (rm -rf
/path/where/the/cache/is), restart squid.
Is there a way
Hi,
is there a way to clear the cache without stopping / rebooting squid?
I usually stop squid, remove the caches from the filesystem (rm -rf
/path/where/the/cache/is), restart squid.
Is there a way to clear that cache without the restart?
Thanks,
Daniele Segato
0 20% 4320
# do not cache everything else
refresh_pattern . 0 20% 0
# see http://wiki.squid-cache.org/KnowledgeBase/DebugSections
#debug_options ALL,3
debug_options 22,3
#debug_options 22,5
Regards,
Daniele Segato
On 04/01/2012 03:21 AM, Amos Jeffries wrote:
Other useful things to know;
Generating an ETag label for each unique output helps caches detect
unique versions without timestamp calculations. The easy ways to do this
are to make ETag a MD5 hash of the body object. Or a hash of the
Last-Modified
On 04/27/2012 07:50 PM, Daniele Segato wrote:
Hi,
I'm experimenting with squid and a service I'm writing.
my service compute ETag and return it along with other Http header
But squid is not sending me the If-None-Match header
I have situation where the Last-Modified date doesn't change
Hi,
I'm experimenting with squid and a service I'm writing.
my service compute ETag and return it along with other Http headers:
Headers returned by a request to my service:
HTTP/1.1 200 OK
Content-Language: it
Cache-Control: public, max-age=60, s-maxage=60
ETag:
(re-send, sent off-list as a mistake)
On 04/01/2012 03:21 AM, Amos Jeffries wrote:
revalidation is more of a threshold which gets set on each object. Under
the threshold no valdation takes place, above it every request gets
validated. BUT ... a 304 response revalutating the object can change
On 04/02/2012 03:22 AM, Amos Jeffries wrote:
Last-Modified: date here, should change when the content change
Cache-Control: public, max-age=60
60 = 60 seconds, means: squid please do not bother the server for 60
seconds after this reply, even if they ask for If-Modified-Since
Small
On 04/02/2012 02:04 AM, Amos Jeffries wrote:
yes I experimented.. I think 60 seconds is perfect for max-age and I
get rid of Expires time, it's overridden by the max-age anyway.
For Squid-3.1+ yes that is true, older HTTP/1.0 software only obeys
Expires:. So it is a matter of whether you want
On 03/30/2012 01:47 AM, Daniele Segato wrote:
Hi,
This is what I want to obtain:
Environment:
* everything on the same machine (Debian GNU\Linux)
* server running on tomcat, port 8080
* squid running on port 280
* client can be anywhere, but for now it's on the localhost machine too
I want
On 03/31/2012 10:13 AM, Amos Jeffries wrote:
On 30/03/2012 12:47 p.m., Daniele Segato wrote:
Instead squid is ALWAYS requiring the resource to the server:
$ curl -v -H 'If-Modified-Since: Thu, 29 Mar 2012 22:14:20 GMT'
'http://localhost:280/alfresco/service/catalog/products'
* About to connect
On 03/31/2012 05:01 PM, Daniele Segato wrote:
On 03/31/2012 10:13 AM, Amos Jeffries wrote:
max-age
The max-age response directive indicates that the response is to
be considered stale after its age is greater than the specified
number of seconds.
The logic goes like this:
Object modified
in this email)
if you need any other information I would gladly provide it.
Thank you very much,
Regards,
Daniele Segato
13 matches
Mail list logo
