[squid-users] Re: server failover/backup
This appears to be a client (192.168.0.125) connecting to what it thinks is a regular forward-proxy port: http_port 3128 or http_port 192.168.0.1:3128 Like i said the clients get the ip and port thru dhcp, thats correct behaivour in my eyes. This above shows Squid receiving various requests for blizzard.com domains and relaying them to the web server at 192.168.0.4. Do you actually have a blizzard.com web server running at 192.168.0.4 ? I dont think so. This is correct. At 192.168.0.4 is a nginx reverse proxy for caching games like steam, origin... and ofc blizzard games. [if i disable squid it works] It seems to me that you are mixing the HTTP traffic modes up. I dont know what you mean. Like i said i dont use this server as a nat, its just a normal server connected to our router. Clients get proxy thru .pac file via dhcp. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667325.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: server failover/backup
I found out why. If i go direct to http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win_deDE-final.MPQ it works (without proxy). If i enable proxy, it wont work and i get 503. BTW i upgraded to Squid Cache: Version 3.3.8 -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667279.html Sent from the Squid - Users mailing list archive at Nabble.com.
RE: [squid-users] Re: server failover/backup
Ideally you should upgrade to 3.4.4 or higher. I was able to download the file just fine through my transparent squid. 503 error is odd, this is an indication of a server side issue but I realize it is coming from squid. Amos, any ideas? -Original Message- From: nuhll [mailto:nu...@web.de] Sent: Wednesday, August 20, 2014 9:51 AM To: squid-users@squid-cache.org Subject: [squid-users] Re: server failover/backup I found out why. If i go direct to http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win _deDE-final.MPQ it works (without proxy). If i enable proxy, it wont work and i get 503. BTW i upgraded to Squid Cache: Version 3.3.8 -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websit es-tp4667121p4667279.html Sent from the Squid - Users mailing list archive at Nabble.com.
RE: [squid-users] Re: server failover/backup
In transparent mode things are working for me just fine including access to battle.net and using the battle client. Does battle.net support proxy configurations? i.e. are you putting the squid IP and Port as a proxy for the client app to use? -Original Message- From: nuhll [mailto:nu...@web.de] Sent: Wednesday, August 20, 2014 9:51 AM To: squid-users@squid-cache.org Subject: [squid-users] Re: server failover/backup I found out why. If i go direct to http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win _deDE-final.MPQ it works (without proxy). If i enable proxy, it wont work and i get 503. BTW i upgraded to Squid Cache: Version 3.3.8 -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websit es-tp4667121p4667279.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: server failover/backup
Hello, thanks for your help. I own a dhcp server which spread the proxy ip:port to all clients (proxy settings are default search for) so all programs are using this proxy automatic for http requests. I use Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3 I worked hard to upgrade to 3.3.8. Im not a linux guru. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667286.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: server failover/backup
Some Logs: == /var/log/squid3/cache.log == 2014/08/20 19:33:19.809 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62595 flags=1 2014/08/20 19:33:20.227 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62378 flags=1 2014/08/20 19:33:20.232 kid1| client_side.cc(900) deferRecipientForLater: clientSocketRecipient: Deferring request http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win_deDE-final.MPQ 2014/08/20 19:33:20.232 kid1| client_side.cc(1518) ClientSocketContextPushDeferredIfNeeded: local=192.168.0.1:3128 remote=192.168.0.125:62611 FD 29 flags=1 Sending next 2014/08/20 19:33:20.235 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62611 flags=1 2014/08/20 19:33:20.638 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62669 flags=1 == /var/log/squid3/access.log == 1408555999.808 10552 192.168.0.125 TCP_MISS/503 3899 GET http://dist.blizzard.com.edgesuite.net/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win-final.MPQ - HIER_DIRECT/192.168.0.4 text/html 1408556000.232 9976 192.168.0.125 TCP_MISS/503 3844 GET http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win-final.MPQ - HIER_DIRECT/192.168.0.4 text/html 1408556000.232 9975 192.168.0.125 TCP_MISS/503 3803 GET http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win_deDE-final.MPQ - HIER_DIRECT/192.168.0.4 text/html 1408556000.638406 192.168.0.125 TCP_MISS/200 1642 CONNECT dws1.etoro.com:443 - HIER_DIRECT/149.126.77.194 - -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667287.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: server failover/backup
I give up. Squid sucks so hard. New and easier idea: accel the sites i want to cache. But how? Information about this is crazy much http://wiki.squid-cache.org/SquidFaq/ReverseProxy But how to cache? # #Recommended minimum configuration: # debug_options ALL,1 33,2 # Example rule allowing access from your local networks. # Adapt to list your (internal) IP networks from where browsing # should be allowed acl localnet src 192.168.0.0/16 acl localnet src fc00::/7 acl localnet src fe80::/10 # RFC1918 possible internal network #acl Safe_ports port 1-65535 # RFC1918 possible internal network #acl CONNECT method GET POST HEAD CONNECT PUT DELETE # RFC1918 possible internal network #acl block-fnes urlpath_regex -i .*/fnes/echo # RFC 4193 local private network range #acl noscan dstdomain .symantecliveupdate.com liveupdate.symantec.com psi3.secunia.com update.immunet.com # RFC 4291 link-local (directly plugged) machines #acl video urlpath_regex -i \.(m2a|avi|mov|mp(e?g|a|e|1|2|3|4)|m1s|mp2v|m2v|m2s|wmx|rm|rmvb|3pg|3gpp|omg|ogm|asf|asx|wmvm3u8|flv|ts) # # Recommended minimum Access Permission configuration: # # Only allow cachemgr access from localhost #no_cache deny noscan #always_direct allow noscan #always_direct allow video # Deny requests to certain unsafe ports # Deny CONNECT to other than secure SSL ports # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on .localhost. is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # #cache_peer 192.168.1.1 parent 8080 0 default no-query no-digest #no-netdb-exchange #never_direct allow all # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed #http_access allow all # allow localhost always proxy functionality # And finally deny all other access to this proxy http_port 192.168.0.8:80 accel defaultsite=windowsupdate.com cache_peer windowsupdate.com parent 80 0 no-query originserver http_port 192.168.0.8:80 accel defaultsite=microsoft.com cache_peer microsoft.com parent 80 0 no-query originserver http_port 192.168.0.8:80 accel defaultsite=windows.com cache_peer windows.com parent 80 0 no-query originserver # We recommend you to use at least the following line. hierarchy_stoplist cgi-bin ? # Uncomment and adjust the following to add a disk cache directory. maximum_object_size 5000 MB #store_dir_select_algorithm round-robin cache_dir aufs /daten/squid 10 16 256 # Leave coredumps in the first cache dir coredump_dir /daten/squid #windows update refresh_pattern -i microsoft.com/.*\.(cab|exe|ms[i|u|f]|asf|wma|dat|zip)$ 202974 80% 262974 refresh_pattern -i windowsupdate.com/.*\.(cab|exe|ms[i|u|f]|asf|wma|dat|zip)$ 202974 80% 262974 refresh_pattern -i windows.com/.*\.(cab|exe|ms[i|u|f]|asf|wma|dat|zip)$ 202974 80% 262974 log_icp_queries off icp_port 0 htcp_port 0 snmp_port 3401 acl snmppublic snmp_community public snmp_access allow snmppublic all minimum_object_size 0 KB buffered_logs on cache_effective_user proxy #header_replace User-Agent Mozilla/5.0 (X11; U;) Gecko/20080221 Firefox/2.0.0.9 vary_ignore_expire on cache_swap_low 90 cache_swap_high 95 #visible_hostname shadow #unique_hostname shadow-DHS shutdown_lifetime 0 second request_header_max_size 256 KB half_closed_clients off max_filedesc 65535 connect_timeout 10 second cache_effective_group proxy #access_log /var/log/squid/access.log squid #access_log daemon:/var/log/squid3/access.test.log squid client_db off #dns_nameservers 192.168.0.10 ipcache_size 1024 fqdncache_size 1024 positive_dns_ttl 24 hours negative_dns_ttl 5 minutes #itcp_outgoing_address 192.168.2.2 dns_v4_first on check_hostnames off forwarded_for delete via off #pinger_enable off #memory_replacement_policy heap LFUDA #cache_replacement_policy heap LFUDA cache_mem 2048 MB maximum_object_size_in_memory 512 KB #memory_cache_mode disk cache_store_log none read_ahead_gap 50 MB pipeline_prefetch on reload_into_ims on #quick_abort_min -1 KB Does not cache any windows updates. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667289.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Re: server failover/backup
On Wednesday 20 August 2014 at 21:08:03 (EU time), nuhll wrote: accel the sites i want to cache. But how? Information about this is crazy much http://wiki.squid-cache.org/SquidFaq/ReverseProxy But how to cache? Simple answer - with a caching proxy server. Longer answer - accelerator mode is incompatible with caching mode - you use either one, or the other, but not both on the same proxy. They're not in the least bit interchangeable, either: - caching mode is where you're running a service for clients (browsers) to improve their performance accessing any server/s - accelerator mode is where you're running a service for servers (websites) to improve their performance (maybe load-balancing, maybe high-availability) for any clients which access them. Caching mode caches, accelerator mode doesn't. From the URL you quoted above: If you wish only to cache the 'rest of the world' to improve local users browsing performance, then accelerator mode is irrelevant. Sites which own and publish a URL hierarchy use an accelerator to improve access to it from the Internet. Sites wishing to improve their local users' access to other sites' URLs use proxy caches. So, accelerator mode or caching mode - different purposes, it's your choice which you need. Antony. -- f u cn rd ths, u cn gt a gd jb n nx prgrmmng Please reply to the list; please *don't* CC me.
Re: [squid-users] Re: server failover/backup
On 21/08/2014 7:22 a.m., Antony Stone wrote: On Wednesday 20 August 2014 at 21:08:03 (EU time), nuhll wrote: accel the sites i want to cache. But how? Information about this is crazy much http://wiki.squid-cache.org/SquidFaq/ReverseProxy But how to cache? Simple answer - with a caching proxy server. Longer answer - accelerator mode is incompatible with caching mode - you use either one, or the other, but not both on the same proxy. This is wrong. Acceleration and caching are simply separate features. They are *independent*, not incompatible. Both forward- and reverse- (accel) proxy can and do cache in exactly the same ways. So nuhll, you will get exactly the same caching behaviour from Squid regardless of using accel mode or a regular proxy port. Only transparent/intercept mode has strange caching behaviours. Amos
Re: [squid-users] Re: server failover/backup
On 21/08/2014 5:29 a.m., nuhll wrote: Hello, thanks for your help. I own a dhcp server which spread the proxy ip:port to all clients (proxy settings are default search for) so all programs are using this proxy automatic for http requests. Not quite. Only the applications which obey DHCP based WPAD auto-configuration. There is also DNS based WPAD, and lots of applications (Java based and mobile apps mostly) which do not auto-configure at all. I use Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3 I worked hard to upgrade to 3.3.8. Im not a linux guru. :-( sorry. The Debian maintainer team has a 3.4 package almost ready but it has been held up by other administrative details for a few months. Amos
Re: [squid-users] Re: server failover/backup
On 21/08/2014 5:33 a.m., nuhll wrote: Some Logs: These logs are showing a problem... == /var/log/squid3/cache.log == 2014/08/20 19:33:19.809 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62595 flags=1 2014/08/20 19:33:20.227 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62378 flags=1 2014/08/20 19:33:20.232 kid1| client_side.cc(900) deferRecipientForLater: clientSocketRecipient: Deferring request http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win_deDE-final.MPQ 2014/08/20 19:33:20.232 kid1| client_side.cc(1518) ClientSocketContextPushDeferredIfNeeded: local=192.168.0.1:3128 remote=192.168.0.125:62611 FD 29 flags=1 Sending next This appears to be a client (192.168.0.125) connecting to what it thinks is a regular forward-proxy port: http_port 3128 or http_port 192.168.0.1:3128 2014/08/20 19:33:20.235 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62611 flags=1 2014/08/20 19:33:20.638 kid1| client_side.cc(777) swanSong: local=192.168.0.1:3128 remote=192.168.0.125:62669 flags=1 == /var/log/squid3/access.log == 1408555999.808 10552 192.168.0.125 TCP_MISS/503 3899 GET http://dist.blizzard.com.edgesuite.net/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win-final.MPQ - HIER_DIRECT/192.168.0.4 text/html 1408556000.232 9976 192.168.0.125 TCP_MISS/503 3844 GET http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win-final.MPQ - HIER_DIRECT/192.168.0.4 text/html 1408556000.232 9975 192.168.0.125 TCP_MISS/503 3803 GET http://llnw.blizzard.com/hs-pod/beta/EU/4944.direct/Updates/hs-6187-6284-Win_deDE-final.MPQ - HIER_DIRECT/192.168.0.4 text/html This above shows Squid receiving various requests for blizzard.com domains and relaying them to the web server at 192.168.0.4. Do you actually have a blizzard.com web server running at 192.168.0.4 ? I dont think so. 1408556000.638406 192.168.0.125 TCP_MISS/200 1642 CONNECT dws1.etoro.com:443 - HIER_DIRECT/149.126.77.194 - It seems to me that you are mixing the HTTP traffic modes up. Squid accepts traffic with two very different on-wire syntax formats, and also with possibly mangled TCP packet details. These combine into 3 perutatiosn we call traffic modes. 1) forward-proxy (aka manual or auto-configured explicit proxy) - port 3128 traffic syntax designed for proxy communication. Nothing special needed to service the traffic. 2) reverse-proxy (aka accelerator / CDN gateway) - port 80 traffic syntax designed for web server communication. Message URLs need reconstructing and an origin cache_peer server is expected to be explicitly configured. 3) interception proxy (aka transparent proxy) - port 80 traffic syntax and also possible TCP/IP mangling of the packet IPs. Any mangling needs to be detected and undone, input validation security checks applied, then the reverse-proxy URL manipulations performed. NP: if the security checks fail caching will be disabled for request, but it will still be serviced as a transparent MISS. NP2: if the security checks fail and the TCP packet details are broken you will get 503 exactly as logged above. What you need to do for a properly working proxy is ensure that: * each mode of traffic is sent to a separate http_port opened by Squid. - you may use multiple port directives as long as each has a unique port number. * each http_port directive is flagged as appropriate to indicate the traffic mode being received there. From the logs above it looks to me like you are possibly intercepting the blizzard traffic and NAT'ing it to a forward-proxy port 3128. You probably need to actually configure this to get rid of the 503s: http_port 3128 http_port 3129 intercept and change your NAT rules to -j REDIRECT packets to port 3129. Leave your DHCP rules sending traffic to port 3128. Amos
RE: [squid-users] Re: server failover/backup
read_ahead_gap 50 MB reload_into_ims on -Original Message- From: nuhll [mailto:nu...@web.de] Sent: Wednesday, August 20, 2014 12:08 PM To: squid-users@squid-cache.org Subject: [squid-users] Re: server failover/backup I give up. Squid sucks so hard. New and easier idea: accel the sites i want to cache. But how? Information about this is crazy much http://wiki.squid-cache.org/SquidFaq/ReverseProxy But how to cache? # #Recommended minimum configuration: # debug_options ALL,1 33,2 # Example rule allowing access from your local networks. # Adapt to list your (internal) IP networks from where browsing # should be allowed acl localnet src 192.168.0.0/16 acl localnet src fc00::/7 acl localnet src fe80::/10 # RFC1918 possible internal network #acl Safe_ports port 1-65535 # RFC1918 possible internal network #acl CONNECT method GET POST HEAD CONNECT PUT DELETE # RFC1918 possible internal network #acl block-fnes urlpath_regex -i .*/fnes/echo # RFC 4193 local private network range #acl noscan dstdomain .symantecliveupdate.com liveupdate.symantec.com psi3.secunia.com update.immunet.com # RFC 4291 link-local (directly plugged) machines #acl video urlpath_regex -i \.(m2a|avi|mov|mp(e?g|a|e|1|2|3|4)|m1s|mp2v|m2v|m2s|wmx|rm|rmvb|3pg|3gpp|omg |ogm|asf|asx|wmvm3u8|flv|ts) # # Recommended minimum Access Permission configuration: # # Only allow cachemgr access from localhost #no_cache deny noscan #always_direct allow noscan #always_direct allow video # Deny requests to certain unsafe ports # Deny CONNECT to other than secure SSL ports # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on .localhost. is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # #cache_peer 192.168.1.1 parent 8080 0 default no-query no-digest #no-netdb-exchange #never_direct allow all # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed #http_access allow all # allow localhost always proxy functionality # And finally deny all other access to this proxy http_port 192.168.0.8:80 accel defaultsite=windowsupdate.com cache_peer windowsupdate.com parent 80 0 no-query originserver http_port 192.168.0.8:80 accel defaultsite=microsoft.com cache_peer microsoft.com parent 80 0 no-query originserver http_port 192.168.0.8:80 accel defaultsite=windows.com cache_peer windows.com parent 80 0 no-query originserver # We recommend you to use at least the following line. hierarchy_stoplist cgi-bin ? # Uncomment and adjust the following to add a disk cache directory. maximum_object_size 5000 MB #store_dir_select_algorithm round-robin cache_dir aufs /daten/squid 10 16 256 # Leave coredumps in the first cache dir coredump_dir /daten/squid #windows update refresh_pattern -i microsoft.com/.*\.(cab|exe|ms[i|u|f]|asf|wma|dat|zip)$ 202974 80% 262974 refresh_pattern -i windowsupdate.com/.*\.(cab|exe|ms[i|u|f]|asf|wma|dat|zip)$ 202974 80% 262974 refresh_pattern -i windows.com/.*\.(cab|exe|ms[i|u|f]|asf|wma|dat|zip)$ 202974 80% 262974 log_icp_queries off icp_port 0 htcp_port 0 snmp_port 3401 acl snmppublic snmp_community public snmp_access allow snmppublic all minimum_object_size 0 KB buffered_logs on cache_effective_user proxy #header_replace User-Agent Mozilla/5.0 (X11; U;) Gecko/20080221 Firefox/2.0.0.9 vary_ignore_expire on cache_swap_low 90 cache_swap_high 95 #visible_hostname shadow #unique_hostname shadow-DHS shutdown_lifetime 0 second request_header_max_size 256 KB half_closed_clients off max_filedesc 65535 connect_timeout 10 second cache_effective_group proxy #access_log /var/log/squid/access.log squid #access_log daemon:/var/log/squid3/access.test.log squid client_db off #dns_nameservers 192.168.0.10 ipcache_size 1024 fqdncache_size 1024 positive_dns_ttl 24 hours negative_dns_ttl 5 minutes #itcp_outgoing_address 192.168.2.2 dns_v4_first on check_hostnames off forwarded_for delete via off #pinger_enable off #memory_replacement_policy heap LFUDA #cache_replacement_policy heap LFUDA cache_mem 2048 MB maximum_object_size_in_memory 512 KB #memory_cache_mode disk cache_store_log none read_ahead_gap 50 MB pipeline_prefetch on reload_into_ims on #quick_abort_min -1 KB Does not cache any windows updates. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websit es-tp4667121p4667289.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: server failover/backup
I got help by email: removed intercept from http port (bc i dont use nat) and removed quick_abort_min. (i got told it bugs sometimes) Still battle.net is not working. I cant believe im the only one with this problem... -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667265.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: server failover/backup
Question: why u spam my thread? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667249.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Re: server failover/backup
On 8/18/2014 4:27 PM, nuhll wrote: Question: why u spam my thread? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667249.html Sent from the Squid - Users mailing list archive at Nabble.com. This is an email list. I created a new email to squid-users@squid-cache.org for assistance from anyone that uses the email list. I was told some time ago that Nabble is not recommended since it does not always place them in a proper layout according to the email user list, so to use it via email, not the website.
Re: [squid-users] Re: server failover/backup
On 19/08/2014 10:48 a.m., Mike wrote: On 8/18/2014 4:27 PM, nuhll wrote: Question: why u spam my thread? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/ONLY-Cache-certain-Websites-tp4667121p4667249.html Sent from the Squid - Users mailing list archive at Nabble.com. This is an email list. I created a new email to squid-users@squid-cache.org for assistance from anyone that uses the email list. I was told some time ago that Nabble is not recommended since it does not always place them in a proper layout according to the email user list, so to use it via email, not the website. Your first email was created as a reply to the thread In-Reply-To: 1408378851794-4667247.p...@n4.nabble.com Amos
