tor 2012-09-13 klockan 12:05 +1200 skrev Amos Jeffries:
Just had a thought. I wonder if this is related to the releases which
people suddenly started having cache MISS for a period with no visible
reason.
That could be the releases where we added/removed methods from the
registered set.
On 09/13/2012 10:07 AM, Henrik Nordström wrote:
We might need to make this the actual method string instead of internal
code to preserve store keys across squid versions.
Well I was wondering about it myself.
and I wanted to ask a thing but still didnt finished investigating about it.
I have
tor 2012-09-13 klockan 12:07 +0300 skrev Eliezer Croitoru:
but in the logs is see a lot:
2012/09/13 11:48:51.798 kid1| StoreEntry::checkCachable: NO: not cachable
Is it a 200 OK response. Suspect it's a 304?
Regards
Henrik
On 09/13/2012 12:12 PM, Henrik Nordström wrote:
Is it a 200 OK response. Suspect it's a 304?
Thanks,
WIll check maybe it is.
..checked..
not 302
a fully 200 response.
1347525419.744116 127.0.0.1 TCP_MISS/200 767 GET
http://www1.ngtech.co.il/302.html - HIER_DIRECT/79.181.232.109 text/html
See http://build.squid-cache.org/job/3.HEAD-ppc-MacOS-Leopard/40/
--
[...truncated 3796 lines...]
sed \
-e s%[@]DEFAULT_HTTP_PORT[@]%3128%g \
-e s%[@]DEFAULT_ICP_PORT[@]%3130%g \
-e s%[@]DEFAULT_CACHE_EFFECTIVE_USER[@]%nobody%g \
ons 2012-09-12 klockan 10:18 +0300 skrev Eliezer Croitoru:
For the no cachable situation something should be done to lower
performance issues that could come from using store_url, some kind of
flag validation before sending it to the helper?
That only helps in the case where we know from
tor 2012-09-13 klockan 11:20 +1200 skrev Amos Jeffries:
I think long-term we want to have ICAP/eCAP generating ETag+Digest
headers for requests and responses and store using those headers as the
index key.
How do you generate an ETag from a request?
ETag is a response header, set by the
See
http://build.squid-cache.org/job/3.2-matrix/./label=sheeva-debian-squeeze/263/
--
Started by upstream project 3.2-matrix build number 263
Building remotely on sheeva-debian-squeeze in workspace
Hello,
As you know, most old squid.conf options cannot handle spaces in
parameter values as they do not support quoted strings or other ways of
escaping the space separator. A few new options, support quoted strings,
but many old ones do not. This is not going to be pretty because there
is no
FYI: There is a 2002 thread on squid-dev about the same problem. Not
sure whether any of the posted patches made it into Squid2, but the
discussion is worth reading anyway:
http://www.squid-cache.org/mail-archive/squid-dev/200211/0153.html
Alex.
On 09/13/2012 07:16 PM, Alex Rousskov wrote:
2) Add squid.conf directives to turn the new parsing behavior on and off
for a section of the configuration file. This is also 100% backward
compatible but difficult to introduce gradually -- admins will expect
everything inside a quoted strings
See http://build.squid-cache.org/job/3.HEAD-ppc-MacOS-Leopard/41/
--
[...truncated 3796 lines...]
sed \
-e s%[@]DEFAULT_HTTP_PORT[@]%3128%g \
-e s%[@]DEFAULT_ICP_PORT[@]%3130%g \
-e s%[@]DEFAULT_CACHE_EFFECTIVE_USER[@]%nobody%g \
See http://build.squid-cache.org/job/3.HEAD-amd64-opensuse/198/changes
Changes:
[Automatic source maintenance] SourceFormat Enforcement
--
[...truncated 7136 lines...]
Testing ../../src/wccp2.h ...Ok.
Testing ../../src/PingData.h ...Ok.
Testing
13 matches
Mail list logo
