Amos Jeffries-2 wrote
> If you need an upgrade to the current version (its worth it)
Indeed, it is. With Debian 8 (testing) and Squid 3.3.8 and identical
IPTABLES & squid.conf configurations the problem with the portal login
doesn't exist.
Thank you very much for the hint, Amos - I would never ha
Thanks Amos for the details - I'll give Debian 8 with 3.3.8 a try, as soon as
I'm less busy.
The support team of the site confirmed me that they use a *non-transparent*
proxy. They further told me that they think my proxy had problems with https
as their login uses it.
Generally, my proxy has no
Antony Stone wrote
> Er, I think you mean "intercept"?
>
> http://www.squid-cache.org/Versions/v3/3.1/cfgman/http_port.html
The "intercept" option is the successor of "transparent"?
>From which Squid version on? The link above doesn't tell.
I run Debian7-shipped Squid3 which is 3.1.20.
Antony
Antony Stone wrote
> Er, I think something got lost along the way there.
Sorry, seems to eat formatted raw text if you use #
> To check it I would only have to change
>
http_port 8080 transparent
>
> to
>
http_port 8080
>
> and restart squid3 service, right?
--
View this message in cont
Antony Stone wrote
> Is there any (security?) reason not to tell us which site this is?
No, but the portal's support staff already checked the issue with the same
configuration (a transparent Squid3 proxy) - and didn't experience the
problem. So I don't see how the Info could help.
Antony Stone
Hi List!
For dozens of WWW portals logins work without problems - but there's one
portal where login fails. Providing your credentials and clicking on the GO
button I get somewhat of a page refresh, but the login fails without error
message. The problem occurs only if my transparent Squid 3.1.20 p
Thanks Antony for your explanation. Sounds reasonable to me.
The thread is marked "solved".
Regards,
Bob
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-doesn-t-overwrite-replace-cached-objects-tp4661911p4661969.html
Sent from the Squid - Users mail
Thanks Antony for your explanation. Sounds reasonable.
As the "production" process of Squid3 runs as user proxy and the cache disk
contents belong to the same user, there shouldn't be a problem for Squid3 to
overwrite/recycle the cached objects.
The thread is marked "resolved".
Regards,
Bob
-
I think, I found the cause myself:
The cache_dir directive had settings from an earlier Squid proxy server,
which had a bigger cache disk. (I C&Ped them when I set up the current proxy
server). It was:
The current Squid server has a cache disk of 20GB and according to the
description of the cac
One more detail:
root@squid3proxy:~# ps -eF|grep squid
root 2852 1 0 11978 3024 0 10:04 ?00:00:00
/usr/sbin/squid3 -YC -f /etc/squid3/squid.conf
proxy 2855 2852 1 58542 165992 0 10:04 ?00:00:51 (squid) -YC
-f /etc/squid3/squid.conf
Squid3 service runs as "root
Hi List,
having run without problems for weeks, from one moment to the following my
Debian 7 based Squid 3.1.20 didn't provide WWW pages anymore to the
connected clients. All networking stuff, included DNS resolution still
worked without problems (ping, nslookup, tracert/traceroute), but the web
b
11 matches
Mail list logo
