[squid-users] Question about version, reverse-proxy and certificate wildcard

Hi, I have a question about certificates wildcard. I have a squid reverseproxy to provide many http servers in only one ip public. The version of my squid is 3.1.19-1ubuntu2. I have setup squid that work with ssl and I have setup a ssl server certificate but this certificate is only correct in

Re: [squid-users] Can not pass Squid basic authentication

On 9/10/2015 3:50 a.m., birbird wrote: > Hi All, > > > I have setup basic authentication for Squid, but I can not get passed from > browser, just asked to inpu user/password time and time again. > > > I was stuck at, the command > /usr/lib64/squid/ncsa_auth /etc/squid/squid_passwd > dose not g

Re: [squid-users] Reverse proxy caching from SSL cache_peer depending on urlpath_regex

On 9/10/2015 11:42 a.m., Manuel wrote: > Hi, > > I am thinking about the idea of using Squid as a reverse proxy on https > (also on http), doing some caching and connecting to a SSL cache_peer and a > non SSL cache_peer depending on the address (e.g. login related addresses > would use the SSL cac

[squid-users] Reverse proxy caching from SSL cache_peer depending on urlpath_regex

Hi, I am thinking about the idea of using Squid as a reverse proxy on https (also on http), doing some caching and connecting to a SSL cache_peer and a non SSL cache_peer depending on the address (e.g. login related addresses would use the SSL cache_peer). The goal is to make faster the browsing

[squid-users] Can not pass Squid basic authentication

Hi All, I have setup basic authentication for Squid, but I can not get passed from browser, just asked to inpu user/password time and time again. I was stuck at, the command /usr/lib64/squid/ncsa_auth /etc/squid/squid_passwd dose not give any output. I think it means squid can not get the auth

[squid-users] SSL Bump and error 14090086

Hello, i have only this problem actually, finally interception works. But in logs, when i access a Https website, i see: fwdNegotiateSSL: Error negotiating SSL connection on FD 14: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed (1/-1/0) WARNING: ssl_crtd #Hlp

Re: [squid-users] Host header forgery detected after upgrade from 3.5.8 to 3.5.9

Since they are using the same dns server there is no need to run some trials. The only test you should in any case test is to see how long is the IP list from the DNS request for the domain name. Eliezer On 08/10/2015 12:12, Roel van Meer wrote: Eliezer Croitoru writes: Are the users and pr

Re: [squid-users] Host header forgery detected after upgrade from 3.5.8 to 3.5.9

Eliezer Croitoru writes: Are the users and proxy using different dns server? No, they are using the same server. Can you run dig from the proxy on this domain and dump the content to verify that the ip is indeed there? I'm currently running with 3.5.8 again, so I'll have to find a quiet h

Re: [squid-users] Host header forgery detected after upgrade from 3.5.8 to 3.5.9

Hey, Are the users and proxy using different dns server? Can you run dig from the proxy on this domain and dump the content to verify that the ip is indeed there? Eliezer On 06/10/2015 14:55, Roel van Meer wrote: Hi everyone, I have a Squid setup on a linux box with transparent interception

Re: [squid-users] Host header forgery detected after upgrade from 3.5.8 to 3.5.9

On 8/10/2015 6:41 p.m., Dan Charlesworth wrote: > Same here—I've been meaning to ask the list about this too. I’m still on > 3.5.9, by the way. > >> On 6 Oct 2015, at 10:55 PM, Roel van Meer wrote: >> >> Hi everyone, >> >> I have a Squid setup on a linux box with transparent interception of both