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

2016-09-08 Thread Eliezer Croitoru
Can it be verified using some kind of dumps? The issues is that if I will try to access https://web.whatsapp.com/ it will probably won't work despite to the fact that I have or do not have a certificate. >From my eyes it's not a certificate issue but rather a websocket one. The simplest way to

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

2016-09-08 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Absolutely right. It is requires to put Whatsapp web to splice rule to make it work. 09.09.2016 2:04, Chico Venancio пишет: > > We had that trouble with whatsapp web. We simply put it in the splice rule. It seems whatsapp checks the client certif

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

2016-09-08 Thread Chico Venancio
We had that trouble with whatsapp web. We simply put it in the splice rule. It seems whatsapp checks the client certificate. Chico Venancio Em 08/09/2016 16:09, "Eliezer Croitoru" escreveu: > Hey, > > Can I reproduce this by just entering the url in > chrome\chromium\firefox\Internet > Exploer

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

2016-09-08 Thread Eliezer Croitoru
Hey, Can I reproduce this by just entering the url in chrome\chromium\firefox\Internet Exploere\Edge\other? I am testing Squid 4 but it's moving slow compared to what I could in the past. I have a squid 4 up and running and I will try to see if I can reproduce it. Can you provide more details abo

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

2016-09-08 Thread erdosain9
Thanks. There you have # Recommended minimum configuration: # # Example rule allowing access from your local networks. # Adapt to list your (internal) IP networks from where browsing # should be allowed #acl localnet src 10.0.0.0/8# RFC1918 possible internal network #acl localnet src 172.16.

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

2016-09-08 Thread Craddock, Tommy
Hello, Show your squid.conf to see how you setup the http_access section.   Tommy E CRADDOCK JR -Original Message- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of erdosain9 Sent: Thursday, September 08, 2016 12:35 PM To: squid-users@lists.squid-cach

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

2016-09-08 Thread erdosain9
Ok. Access.log 1473352640.832514 192.168.1.172 TCP_MISS/200 527 GET https://web.whatsapp.com/status.json - HIER_DIRECT/31.13.85.51 text/json 1473352642.737290 192.168.1.172 TCP_MISS/404 464 GET https://web.whatsapp.com/404.appcache - HIER_DIRECT/31.13.85.51 text/html 1473352643.237143

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

2016-09-08 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Show access.log, not screenshot. 08.09.2016 18:38, erdosain9 пишет: > Finally i update to squid 3.5 and try the acl with dstdomain > > > Craddock, Tommy wrote >> Hello, >> Create an ACL that will be a list of domains, either in the ACL or in a >>

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

2016-09-08 Thread erdosain9
Finally i update to squid 3.5 and try the acl with dstdomain Craddock, Tommy wrote > Hello, > Create an ACL that will be a list of domains, either in the ACL or in a > txt file that the ACL refers to, and place any URLs you want bypassed by > the proxy into the ACL. Something like this: > ACL S

Re: [squid-users] Transparent Proxy

2016-09-08 Thread Amos Jeffries
On 8/09/2016 11:54 p.m., John Sayce wrote: > Yeah, that was the key. I was expecting my firewall to be doing NAT but > destination NAT rather than source NAT. I hadn't realised this was > completely wrong. > > Got it working now. Source-NAT is fine and sometimes needed to translate between

Re: [squid-users] Transparent Proxy

2016-09-08 Thread John Sayce
Yeah, that was the key. I was expecting my firewall to be doing NAT but destination NAT rather than source NAT. I hadn't realised this was completely wrong. Got it working now. Thanks -Original Message- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf

Re: [squid-users] TProxy and client_dst_passthru

2016-09-08 Thread Antony Stone
On Thursday 08 September 2016 at 12:27:42, Omid Kosari wrote: > Hi Fred, > > Same problem here . Do you found any solution or workaround ? Please clarify which message you are reply / referring to. Thanks, Antony. -- Archaeologists have found a previously-unknown dinosaur which seems to hav

Re: [squid-users] TProxy and client_dst_passthru

2016-09-08 Thread Omid Kosari
Hi Fred, Same problem here . Do you found any solution or workaround ? Regards -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TProxy-and-client-dst-passthru-tp4670189p4679422.html Sent from the Squid - Users mailing list archive at Nabble.com.

Re: [squid-users] Transparent Proxy

2016-09-08 Thread Antony Stone
On Thursday 08 September 2016 at 10:44:12, John Sayce wrote: > After I wrote this I realised it should be changing the mac not the ip, > which is not what’s happeneing. I think it's my firewall configuration > that's wrong. In that case your firewall is doing NAT instead of policy routing. Rega

Re: [squid-users] Transparent Proxy

2016-09-08 Thread John Sayce
After I wrote this I realised it should be changing the mac not the ip, which is not what’s happeneing. I think it's my firewall configuration that's wrong. Thanks -Original Message- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of Antony Stone Sent:

Re: [squid-users] Transparent Proxy

2016-09-08 Thread Antony Stone
On Thursday 08 September 2016 at 10:12:48, John Sayce wrote: > For testing purposes I've reduced it to the following: > > http_port 3128 intercept > #dns_v4_first on > dns_nameservers 10.8.2.3 194.168.4.100 10.8.2.2 8.8.8.8 > acl wifi src 10.8.14.0/24 > acl all src all > http_access allow all > m

Re: [squid-users] Transparent Proxy

2016-09-08 Thread John Sayce
For testing purposes I've reduced it to the following: http_port 3128 intercept #dns_v4_first on dns_nameservers 10.8.2.3 194.168.4.100 10.8.2.2 8.8.8.8 acl wifi src 10.8.14.0/24 acl all src all http_access allow all maximum_object_size 1 GB minimum_object_size 0 KB maximum_object_size_in_memory 4