Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On Mon, 2016-10-24 at 21:05 +0500, Garri Djavadyan wrote: > On 2016-10-24 19:40, Garri Djavadyan wrote: > > > > So, the big G sends 304 only to HEAD requests, although it is a > > violation [1], AIUI: > > > > curl --head -H 'If-Modified-Since: Thu, 20 Oct 2016 08:29:09 GMT' > > -H > >

Re: [squid-users] External nat'ed transparent proxy

+1 for Amos direction. I am still trying to understand what is the difference between a router and a switch since they seems to have the same CPU but missing one or two embedded instructions. Eliezer Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email:

Re: [squid-users] Web Whatsapp, Dropbox... problem

It took me a while and I hope that I will be able to get the dumps this week. I started working on an example of ebtables level traffic redirection towards the squid machine. The scenario should be a good example for embedded devices which operates mostly food in the bridge level rather then the

Re: [squid-users] Squid with ASR9001

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 No, Juniper is not my area ;) It is impossible to know everything :) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYDpOEAAoJENNXIZxhPexGUWEH/jdttWLpJNQm49z0XlTMwwIM

Re: [squid-users] Squid with ASR9001

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Compared with PBR - definitely. IF OS TCP stack supports bridging - exactly. 25.10.2016 3:59, Eliezer Croitoru пишет: > So what you are illustrating is that if we will handle the connection > interception using bridge tables it would be much

Re: [squid-users] Squid with ASR9001

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ah - in Squid's wiki don't pay attention on Variant III. This is minimalistic topology, main goal was as minimum hardware units as possible (for cost minimization). Also VRF-variant still in progress. We can't solve DNS proxying task as required

Re: [squid-users] Squid with ASR9001

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Well, if we're talking about squid-based appliances. http://wiki.squid-cache.org/ConfigExamples/Intercept/CiscoIOSv15Wccp2 In this article descrived approx. half-year experimental experience with various LAN topologies, and Cisco devices.

Re: [squid-users] sourcehash load balance

On 23/10/2016 10:35 a.m., Amos Jeffries wrote: On 22/10/2016 12:21 a.m., André Janna wrote: I set up a Squid proxy that forwards all requests to 2 parent caches. I'm using Squid version 3.5.19. My goal is that multiple connection from a client to a server should be forwarded to the same

Re: [squid-users] Squid with ASR9001

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 No. 24.10.2016 23:40, Eliezer Croitoru пишет: > And why would you want this exactly? > The most simple thing is to use routing policy and to monitor the proxy in > a much higher level then WCCP. Based on my personal experience with WCCP (over 6

Re: [squid-users] skype connection problem

Just to understand the scenario: You have let say 1 client on network 192.168.0.0/24 You have a proxy at 192.168.0.200 The client doesn’t have a gateway in the network IE cannot run dns queries or pings to the internet. The client must define the proxy in order to access any Internet resources.

Re: [squid-users] skype connection problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 24.10.2016 22:28, Nicolas Valera пишет: > > > On 10/24/2016 01:21 PM, Yuri Voinov wrote: >> > > 24.10.2016 22:19, Nicolas Valera пишет: > >>> Hi Yuri, thanks for the answer! > >>> > >>> we don't have the squid in transparent mode in this

Re: [squid-users] skype connection problem

On 10/24/2016 01:21 PM, Yuri Voinov wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 24.10.2016 22:19, Nicolas Valera пишет: Hi Yuri, thanks for the answer! we don't have the squid in transparent mode in this network. So, you route all traffic to proxy box? Yes, clients do not

Re: [squid-users] skype connection problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 24.10.2016 22:19, Nicolas Valera пишет: > Hi Yuri, thanks for the answer! > > we don't have the squid in transparent mode in this network. So, you route all traffic to proxy box? > the squid configuration is very basic. here is the conf: > >

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 24.10.2016 22:05, Garri Djavadyan пишет: > On 2016-10-24 19:40, Garri Djavadyan wrote: >> So, the big G sends 304 only to HEAD requests, although it is a >> violation [1], AIUI: >> >> curl --head -H 'If-Modified-Since: Thu, 20 Oct 2016 08:29:09

Re: [squid-users] skype connection problem

Hi Yuri, thanks for the answer! we don't have the squid in transparent mode in this network. the squid configuration is very basic. here is the conf: - http_port 1280 connection-auth=off forwarded_for delete

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 2016-10-24 19:40, Garri Djavadyan wrote: So, the big G sends 304 only to HEAD requests, although it is a violation [1], AIUI: curl --head -H 'If-Modified-Since: Thu, 20 Oct 2016 08:29:09 GMT' -H 'If-None-Match: "101395"' http://dl.google.com/linux/direct/google-chro

Re: [squid-users] Error "ipcacheParse: No Address records in response to"

By the way... When i get this error 2016/10/24 12:13:36 kid1| ipcacheParse: No Address records in response to 'client.wns.windows.com' 2016/10/24 12:13:36 kid1| ipcacheParse: No Address records in response to 'client.wns.windows.com' 2016/10/24 12:13:36 kid1| ipcacheParse: No Address records

[squid-users] Error "ipcacheParse: No Address records in response to"

Hi. The squid was working perfect... but, i need to change the router (for some problems). So im using a Juniper Firewall like router... So, now i have this error 2016/10/24 12:13:27 kid1| WARNING: All 32/32 ssl_crtd processes are busy. 2016/10/24 12:13:27 kid1| WARNING: 32 pending requests

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

I'm sorry to interrupt - I remember someone saying that you need to always abide by RFC? Well, as you say it to Google? 24.10.2016 20:40, Garri Djavadyan пишет: On Tue, 2016-10-25 at 01:22 +1300, Amos Jeffries wrote: On 25/10/2016 12:32 a.m., Garri Djavadyan wrote: On Mon, 2016-10-24 at

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On Tue, 2016-10-25 at 01:22 +1300, Amos Jeffries wrote: > On 25/10/2016 12:32 a.m., Garri Djavadyan wrote: > > > > On Mon, 2016-10-24 at 23:51 +1300, Amos Jeffries wrote: > > > > > > On 24/10/2016 9:59 p.m., Garri Djavadyan wrote: > > > > > > > > Nevertheless, the topic surfaced new details

Re: [squid-users] ERROR: Cannot connect to 127.0.0.1:3128

On 24/10/2016 9:34 p.m., Михаил wrote: > Hi! > Could you write me if you had managed to emulate the problem that I have? > Best regards, Misha. I have not been able to replicate it here. I think I remember seeing it a few years back, but not recently and trying last week my Squid worked okay. I

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 25/10/2016 12:32 a.m., Garri Djavadyan wrote: > On Mon, 2016-10-24 at 23:51 +1300, Amos Jeffries wrote: >> On 24/10/2016 9:59 p.m., Garri Djavadyan wrote: >>> Nevertheless, the topic surfaced new details regarding the Vary and >>> I >>> tried conditional requests on same URL (Google Chrome)

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 24/10/2016 11:49 p.m., Yuri wrote: > > > 24.10.2016 16:42, Alex Crow пишет: >> On 24/10/16 11:26, Yuri wrote: >> >>> No, Amos, I'm not trolling your or another developers. >>> >>> I just really do not understand why there is a caching proxy, which >>> is almost nothing can cache in the modern

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On Mon, 2016-10-24 at 23:51 +1300, Amos Jeffries wrote: > On 24/10/2016 9:59 p.m., Garri Djavadyan wrote: > > Nevertheless, the topic surfaced new details regarding the Vary and > > I > > tried conditional requests on same URL (Google Chrome) from > > different > > machines/IPs. Here results: > >

Re: [squid-users] external_acl_type problem

>But the startup should be 0 in all Squid-3.2+ like you say. Are you applying any patches to external_acl.cc or helper/ChildConfig.cc ? < No patches. Now I rebuilt squid on a 32-bit debian, with default ./configure opts. Same effect: 2016/10/24 09:54:09 kid1| helperOpenServers: Starting 5/5

Re: [squid-users] Squid with ASR9001

Ha, it seems ASR9000 really does not support WCCP exactly. You right. WCCP supported on Nexus, on ASR1000... So, your router only can use PBR or analoquie. The only idea is to buy 3750 as aggregation switch, config WCCP on it and connect to your ASR by fiber trunk. 24.10.2016 16:30, Garth

Re: [squid-users] [External] Re: Issue when connecting to apple APN

Dears, Finally we found the issue as we are running squid on RHEL 7 Service dnsmasq was stopped We just start it and everything worked fine ! علاء حسن جميل برقاوي Ala'a Hasan Jamil Barqawi System Integrator 8191 Takhassusi Road, Olaya Riyadh 12333 - 3038, KSA Tel +(9661) 2887513 Mobile +(966)

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 24/10/2016 9:59 p.m., Garri Djavadyan wrote: > Hi Amos, > > Thank you very much for so detailed explanation. I've made conclusions > from presented information. I deeply regret, that the topic took so > many time from you. I believe, information presented here will be > helpful for the

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

24.10.2016 16:42, Alex Crow пишет: On 24/10/16 11:26, Yuri wrote: No, Amos, I'm not trolling your or another developers. I just really do not understand why there is a caching proxy, which is almost nothing can cache in the modern world. And that in vanilla version gives a maximum of

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 24/10/16 11:26, Yuri wrote: No, Amos, I'm not trolling your or another developers. I just really do not understand why there is a caching proxy, which is almost nothing can cache in the modern world. And that in vanilla version gives a maximum of 10-30% byte hit. From me personally, it

Re: [squid-users] Squid with ASR9001

By Cisco employee - “Correct, there is no WCCP and no plans for it either... :(” https://supportforums.cisco.com/discussion/12227051/ios-xr-and-wccp WCCP supported platforms – https://supportforums.cisco.com/document/133201/wccp-platform-support-overview Our ASR9001 has no

Re: [squid-users] [External] Re: Issue when connecting to apple APN

I used the same configuration as this URL https://panaharjuna.wordpress.com/2009/12/17/speed-your-squid-server-using-google-public-dns/ But unfortunately when it comes to resolve the apple APN gateway it failed and return 503 service unavailable Any hope to solve it please? Access.log

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

No, Amos, I'm not trolling your or another developers. I just really do not understand why there is a caching proxy, which is almost nothing can cache in the modern world. And that in vanilla version gives a maximum of 10-30% byte hit. From me personally, it needs no justification and no

Re: [squid-users] Squid with ASR9001

24.10.2016 13:16, Garth van Sittert | BitCo пишет: Yes, it looks like all of the ASR9000 range which makes use of IOS XR no longer supports WCCP. Please, provide prooflink from Cisco. Policy Based Routing has been replaced by ACL Based Forwarding or ABF. So? This is therminology

Re: [squid-users] Issue when connecting to apple APN

On Monday 24 October 2016 at 11:36:34, Antony Stone wrote: > On Monday 24 October 2016 at 11:27:17, Alaa Hassan Barqawi wrote: > > Dears, > > I am facing issue in connecting with apple APN gateway.push.apple.com : > > 2195 The name cannot be resolved although I am using google DNS servers > > and

Re: [squid-users] Issue when connecting to apple APN

On Monday 24 October 2016 at 11:27:17, Alaa Hassan Barqawi wrote: > Dears, > I am facing issue in connecting with apple APN gateway.push.apple.com : > 2195 The name cannot be resolved although I am using google DNS servers > and it throws an error Unable to determine IP address from host name >

[squid-users] Issue when connecting to apple APN

Dears, I am facing issue in connecting with apple APN gateway.push.apple.com : 2195 The name cannot be resolved although I am using google DNS servers and it throws an error Unable to determine IP address from host name gateway.push.apple.com The DNS server returned: No DNS records Thanks for

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On Mon, 2016-10-24 at 19:03 +1300, Amos Jeffries wrote: > On 24/10/2016 6:28 a.m., gar...@comnet.uz wrote: > > > > On 2016-10-23 18:31, Amos Jeffries wrote: > > > > > > On 23/10/2016 2:32 a.m., garryd wrote: > > > > > > > > Since I started use Squid, it's configuration always RFC > > > >

Re: [squid-users] ERROR: Cannot connect to 127.0.0.1:3128

Hi!Could you write me if you had managed to emulate the problem that I have? Best regards, Misha.   14.10.2016, 18:51, "Михаил" :Hi.Ready. # squidclient -vv mgr:info | head -n 40stub time| WARNING: BCP 177 violation. IPv6 transport forced OFF by build parameters.verbosity

Re: [squid-users] Squid with ASR9001

Yes, it looks like all of the ASR9000 range which makes use of IOS XR no longer supports WCCP. Policy Based Routing has been replaced by ACL Based Forwarding or ABF. From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of Yuri Voinov Sent: Sunday, 23 October 2016

Re: [squid-users] external_acl_type problem

On 23/10/2016 11:39 p.m., reinerotto wrote: > 1) > According to > http://www.squid-cache.org/Doc/config/external_acl_type/ > > in squid.conf, this > > external_acl_type check_delay ttl=0 cache=0 %SRC /etc/squid/check_delay.sh > > should start 0 helpers immediately after squid (3.5.22)

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 24/10/2016 6:28 a.m., gar...@comnet.uz wrote: > On 2016-10-23 18:31, Amos Jeffries wrote: >> On 23/10/2016 2:32 a.m., garryd wrote: >>> Since I started use Squid, it's configuration always RFC compliant by >>> default, _but_ there were always knobs for users to make it HTTP >>> violent. It was