It's pretty famous.
I have even used it for sometime in the past and from many firewall
distros it was one of the good ones.
Eliezer
On 26/07/2015 18:26, Stanford Prescott wrote:
The OS is Smoothwall Express v3.1. A linux firewall distro not really based
on any other of the major distros.
I have squid configured as a forward proxy with basic authentication. All
traffic flows as expected, but periodically I get an authentication pop-up
indicating an origin server is requiring credentials. I check the URL via
non-proxy browser and does not ask for proxy credentials? So to
Thanks for the props about Smoothwall. For SOHO environments, it's one of
the best, IMHO. But then, I am not prejudiced at all. ;-)
On Mon, Jul 27, 2015 at 7:33 AM, Eliezer Croitoru elie...@ngtech.co.il
wrote:
It's pretty famous.
I have even used it for sometime in the past and from many
The developers of Smoothwall Express v3.1 have been trying to address this
issue for a few days now. We have had users complaining of this same issue
with Squid 3.5.5 and 3.5.6. It didn't seem to happen with prior versions.
We (or at least our lead developer Neal Murphy) thinks it is related to
On Monday 27 Jul 2015 at 16:53, Berkes, David wrote:
I have squid configured as a forward proxy with basic authentication. All
traffic flows as expected, but periodically I get an authentication pop-up
indicating an origin server is requiring credentials. I check the URL via
non-proxy
On Monday 27 Jul 2015 at 18:45, HackXBack wrote:
how i can use useragent log in 3.5.6
while no user agent log in access.log like it mentioned in
http://wiki.squid-cache.org/SquidFaq/SquidLogs
As the page says this log has become one of the default access.log formats
and is always available
Here is the information requested. From the log, everything looks to be
normal. The log example is from the cdn0.vox-cdn.com traffic.
ORIGIN URL's
pixel.adsafeprotected.com
cdn0.vox-cdn.com
sb.scorecardresearch.com
SQUID LOG
access.log.2:1437683164.693 0 70.197.241.219
The version numbering you have identified seems to coincide with my issues
as well. I moved to the newer versions of squid for the newer enhanced ssl
bumping features but ran into this issue. I was hoping my stacktrace would
finally allow the squid developers to identify and resolve the issue.
Thanks. Here is my feedback.
1. what page do you see if you fail to authenticate correctly - is it from the
origin server cdn0.vox-cdn.com (in this case) or is it the page your users
would see if they failed to correctly authenticate to squid in the first place?
When the origin server
On Monday 27 Jul 2015 at 17:21, Berkes, David wrote:
Here is the information requested. From the log, everything looks to be
normal. The log example is from the cdn0.vox-cdn.com traffic.
ORIGIN URL's
pixel.adsafeprotected.com
cdn0.vox-cdn.com
sb.scorecardresearch.com
SQUID
iPhones and mysterious auth popups on CONNECT requests where the cancel
continues as if nothing happened.
Sounds very familiar.
Each time so far that I've been through and debugged these symptoms in
detail it has turned out Squid was working correctly. The 407 were
correct normal HTTP responses
Running into an issue, using the squid.conf entry
dns_nameservers 72.x.x.x 72.x.y.y
These are different servers (under our control) for the purpose of
filtering than listed in resolv.conf (which are out of our control, used
for server IP routing by upstream host).
The problem we found like
this log format didnt work and no thing about useragent in access.log
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/useragent-log-tp4672505p4672508.html
Sent from the Squid - Users mailing list archive at Nabble.com.
On 28/07/2015 9:06 a.m., HackXBack wrote:
this log format didnt work and no thing about useragent in access.log
Works for me...
squid.conf:
access_log stdio:/var/logs/UA.log useragent
# squidclient http://example.com/ /dev/null
# tail /var/logs/UA.log
::1 [27/Jul/2015:14:53:10
On 28/07/2015 8:38 a.m., Mike wrote:
Running into an issue, using the squid.conf entry
dns_nameservers 72.x.x.x 72.x.y.y
These are different servers (under our control) for the purpose of
filtering than listed in resolv.conf (which are out of our control, used
for server IP routing by
Thanks Amos, i have removed the generate-host-certificates
http_port 0.0.0.0:3128 ssl-bump dynamic_cert_mem_cache_size=4MB
cert=/etc/squid3/ssl/chain.pem
But Squid still not want load the couple of Ca and certificate.
2015/07/27 10:16:30| Using certificate in
16 matches
Mail list logo
