Good morning,
We have a special requirement and we are not sure whether it's possible to
accomplish.
We have defined a whitelist and a blacklist on our Squid. Its behaviour is
as usual and how it could expect.
All the traffic less blacklist is passed however we are interested to get
an alert abo
Hello
what is the essential difference between the default squid package and
this squid34 package,
as I have problems using this squid34 package for FTP connections;
there are no shown icons, when going to e.g. ftp://ftp.adobe.com/
when I tell the browser to show the image then I get this squid
On 25.05.2017 09:51, Miguel Barbero wrote:
Good morning,
We have a special requirement and we are not sure whether it's
possible to accomplish.
We have defined a whitelist and a blacklist on our Squid. Its
behaviour is as usual and how it could expect.
All the traffic less blacklist is pas
On 25/05/17 19:51, Miguel Barbero wrote:
Good morning,
We have a special requirement and we are not sure whether it's
possible to accomplish.
We have defined a whitelist and a blacklist on our Squid. Its
behaviour is as usual and how it could expect.
All the traffic less blacklist is passe
On 25/05/17 20:19, Walter H. wrote:
Hello
what is the essential difference between the default squid package and
this squid34 package,
Run "squid -v" to find out if there are any build options different.
Usually its just two alternative versions from the vendor.
as I have problems using
Yay! It works! I got the Firefox addon Foxyproxy and checked the little SSL
box, and it works perfectly.
How frustrating is it that Firefox and Chrome don't have this as an easy box to
check? They say it will cause confusion, but how many people even use a proxy
to begin with?
From
On 25.05.2017 11:25, Amos Jeffries wrote:
On 25/05/17 19:51, Miguel Barbero wrote:
Good morning,
We have a special requirement and we are not sure whether it's
possible to accomplish.
We have defined a whitelist and a blacklist on our Squid. Its
behaviour is as usual and how it could expect
Thought I'd try getting this to work in Chrome too. NOTHING I try makes it
work in Chrome. Isn't running this from the Windows command line supposed to
work?
chrome --proxy-server=https://mydomain:myport
When I do this, it runs Chrome, but it's still not going through the proxy
despite Firefox
If you use foxyproxy for firefox, you can use switchysharp for Chrome.
Marcus
On 25/05/17 09:00, j m wrote:
Thought I'd try getting this to work in Chrome too. NOTHING I try makes it
work in Chrome. Isn't running this from the Windows command line supposed to
work?
chrome --proxy-server=h
This doesn't seem to have the SSL option like Foxyproxy does.
From: Marcus Kool
To: squid-users@lists.squid-cache.org
Sent: Thursday, May 25, 2017 8:18 AM
Subject: Re: [squid-users] SSL bump, SSL intercept, explicit, secure proxy,
what is it called?
If you use foxyproxy for firef
On 25.05.2017 12:50, Amos Jeffries wrote:
On 25/05/17 20:19, Walter H. wrote:
Hello
what is the essential difference between the default squid package
and this squid34 package,
Run "squid -v" to find out if there are any build options different.
Usually its just two alternative versions fro
Walter, what I've found is when compiling to squid 3.5.x and higher, the
compile options change. Also remember that many of the options that were
available with 3.1.x are depreciated and likely will not work with 3.4.x
and higher.
The other issue is that squid is only supposed to be handling H
Hello Dear Squid Users,
I am trying to configure my Squid 4.0.17 to use an https connection between
the client and the proxy. I have added an https_port directive to
squid.conf, but it must be misconfigured. When I test with a dev version of
curl that supports https proxies, I am getting
ERR_PROT
13 matches
Mail list logo
