Re: AW: [squid-users] Troubleshooting squid: modified content

Sig Pam:
> Jeff, thank you for your kind support.
>
> The technical description of my setup follows, after comments on your reply.
>
> If I get your config change correct, you bypass the squid proxying by using
> kb.4d.com as a peer cache, right? Why do you do this? Were you able to
> verify my problem if you run your squid WITHOUT your additional lines?
>

In last message I added those lines to squid.conf, that means I'm using
squid as a reverse proxy.
If you are not using reverse proxy, please ignore them.

OK I adjust my squid as a common proxy, and tested your site
(http://kb.4d.com/).
All goes fine with the config below.
I'm using Squid3.0-stable14, so you may be using this version of squid.

http_port 8080
icp_port 0
hierarchy_stoplist cgi-bin ?
cache_mem 1600 MB
maximum_object_size 20480 KB
maximum_object_size_in_memory 1024 KB
memory_pools_limit 100 MB
shutdown_lifetime 10 seconds
cache_replacement_policy heap GDSF
memory_replacement_policy heap GDSF
cache_dir aufs /data/cache 51200 16 256
access_log /data/logs/access.log
cache_log /data/logs/cache.log
cache_store_log none
logfile_rotate 6
strip_query_terms off
pid_filename /data/logs/squid.pid
coredump_dir /data/logs
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern (cgi-bin|\?) 0 0% 0
refresh_pattern . 0 20% 900
acl manager proto cache_object
acl localhost src 127.0.0.1/32
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443
acl Safe_ports port 80 443
acl CONNECT method CONNECT
acl PURGE method PURGE
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow PURGE localhost
http_access deny PURGE
http_access allow all
http_reply_access allow all

-- 
Jeff Pang
DingTong Technology
www.dtonenetworks.com