I recently noticed one of my squid servers reverse its normal usage stats
for:
Request Memory Hit Ratios: 5min: 0.6%, 60min: 0.5%
Request Disk Hit Ratios:5min: 41.7%, 60min: 48.3%
Normal usage looks more like:
Request Memory Hit Ratios:
Hi all,
I recently noticed one of my squid servers reverse its normal usage stats for:
Request Memory Hit Ratios: 5min: 0.6%, 60min: 0.5%
Request Disk Hit Ratios:5min: 41.7%, 60min: 48.3%
Normal usage looks more like:
Request Memory Hit Ratios: 5min:
Hi Amos,
Is there any http://domain:port; part on the URL when it arrives at
Squid?
No.
vport=80 on the http_port 8443 line.
This solved it. Thanks.
Regards,
Sean.
This e-mail is confidential. If you are not the intended recipient you must not
disclose or use the information
Hi Amos,
have to have port :8443 as the destination port. Since origin requests
have the domain:port part in the Host: header
A minor correction here. The SSL offload device (Nortel Application Switch)
does some networking magic so neither the originating request nor the forwarded
request
Hi all,
I'm running squid/2.6.STABLE21 behind an SSL offload appliance on port 8443 as
an application accelerator.
squid.conf:
http_port 10.67.124.57:80 accel vhost protocol=http
http_port 10.67.124.57:8443 accel vhost protocol=http
cache_peer 127.0.0.1 Parent 80 0 no-query no-digest default
Hi all,
I'm trying different things here to no avail:
acl monitoring src 139.230.80.11/32 139.230.244.129/32 10.67.124.6/32
10.67.124.8/32
access_log /var/log/squid/access.log common !monitoring
Any suggestions? Anyone?
Or is this something too simple to warrant a response and I should just
I'm testing 2.7 and these (slightly obsfucated) lines from our working
2.6 config no longer appear to be working
FOUND IT!
log_access directive is required. Maybe a bug in 2.6?
acl monitoring src 139.230.80.11/32 139.230.244.129/32 10.67.124.6/32
10.67.124.8/32
log_access deny monitoring
Hi all,
I'm testing 2.7 and these (slightly obsfucated) lines from our working 2.6
config no longer appear to be working, ie. requests from these IPs are being
logged.
acl monitoring1 src XXX.XXX.80.11
acl monitoring2 src XXX.XXX.244.129
acl monitoring3 src 10.67.124.6
acl monitoring4 src
Hi Matus,
I'd say this it misbehaviour of the solution. I guess a simple Vary:
header containing the name of the header inserted by ssl offload device
should do it.
That did it. Thanks.
Apache conf example:
Header append Vary X-SSL
--
Rgds,
Sean.
This e-mail is
Hi all,
I'm wondering if (and how) a single squid installation can be configured to
treat 2 different ports on the same parent as different caches?
I have an application behind squid, using it as an accelerator, that responds
with different content to requests for the same URL based on the
Hi All,
I recently copied an existing system from one server onto another where we're
using squid as a reverse proxy. After starting everything up certain files from
the site, ie. images, css, wouldn't load properly.
Here, I believe, is a relevant line from store.log for one of the images that
Hi All,
I recently copied an existing system from one server onto another where we're
using squid as a reverse proxy. After starting everything up certain files from
the site, ie. images, css, wouldn't load properly.
Here, I believe, is a relevant line from store.log for one of the images that
Hi all,
I'm a squid newbie and struggling with getting Cache Manager working. I keep
getting:
Access Denied.
Access control configuration prevents your request from being allowed at this
time.
What am I missing?
Here's our squid.conf:
emulate_httpd_log on
cache_dir ufs /squid_cache/squid
13 matches
Mail list logo
