I worked a fix:
diff --git a/squid-3.5.1/src/client_side.cc b/squid-3.5.1/src/client_side.cc
index d72e8c4..025316d 100644
--- a/squid-3.5.1/src/client_side.cc
+++ b/squid-3.5.1/src/client_side.cc
@@ -3045,7 +3045,8 @@ ConnStateData::parseProxy1p0()
debugs(33, 5, "PROXY/1.0 protocol on co
Hello,
I believe you're experiencing bug 3329:
http://bugs.squid-cache.org/show_bug.cgi?id=3329
Please try the patch that I have on there and see if that helps your issue.
Thank you,
Nathan.
On 15 April 2015 at 07:16, HackXBack wrote:
> [New LWP 4677]
> [New LWP 4704]
> [New LWP 4687]
> [New
Hi all,
If I configure a new delay pool in the config file or reconfigure an
existing delay pool, do I have to restart squid? Can I send a SIGHUP to it
to re-read the config file instead ? If I send a SIGHUP, what would happen
to downloads that are in progress ?
Thanks,
Hector
_
I found out what is wrong, but I am not familar to squid code, so I post
here to see if someone can show me the next step:
The problem is at this part of code:
void
ClientHttpRequest::sslBumpStart()
{
debugs(85, 5, HERE << "Confirming " << Ssl::bumpMode(sslBumpNeed_) <<
"-bumped CON
Squid version 3.5.3.
When the http response received by Squid contains a no-cache="set-cookie", the
response is not cached. cache.log has the line:
2015/04/14 18:24:38.027 kid1| http.cc(359) cacheableReply: NO because server
reply Cache-Control:no-cache has parameters
The relevant source code is
Possile Problem #1:
digest_pw_auth has not existed in some years. The helpers correct
current name is digest_file_auth. Please upgrade.
In the openwrt repository, I can only find Squid 2.7, and I can't upgrade
to newer.
Can I make this work somehow, with the current setup?
Possible Problem #2:
[New LWP 4677]
[New LWP 4704]
[New LWP 4687]
[New LWP 4702]
[New LWP 4695]
[New LWP 4725]
[New LWP 4697]
[New LWP 4490]
[New LWP 4493]
[New LWP 4473]
[New LWP 4508]
[New LWP 4495]
[New LWP 4460]
[New LWP 4511]
[New LWP 4516]
warning: Can't read pathname for load map: Input/output error.
[Thread de
Hi Guy,
Thanks for answering :o)
Based on the bugzilla, it's fixed but not yet available.
Anyway, that's a very good news.
Let's wait the next build.
Thanks for your help.
Bye Fred
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Random-SSL-bump-DB-corrupti
> On Apr 14, 2015, at 3:40 PM, Stakres wrote:
>
> Hi All,
>
> No reply ?
> Do we have to leave with this mega/crazy bug ?
> Is there someone in the Squid team able to have a look to this problem or
> nobody care ?
>
> Thanks in advance.
>
> Bye Fred
>
The issue I’m aware of (bug 4212) has b
Hi All,
No reply ?
Do we have to leave with this mega/crazy bug ?
Is there someone in the Squid team able to have a look to this problem or
nobody care ?
Thanks in advance.
Bye Fred
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Random-SSL-bump-DB-corrupt
Hello Amos,
Thank you for your reply.
> Problem A)
> requirements #1 and #2 above are mutually exclusive.
>
> Obeying #1 involves sending traffic from Squid to the parent proxy for
> action.
>
> Obeying #2 involves opening direct TLS connections from Squid to the
> origin servers.
Is it possib
> > Could anyone offer any suggestions or advice to help figure out what is
> causing these problems?
>
> 1) upgrade.
>
> 2) seriously, upgrade.
>
> 3) try adding "via on" to your squid.conf. If you start to get warnings about
> forwarding loops its working. Otherwise you got big problems - see
I think, in the sslbump mode, if PROXY protocol is enabled, client cannot
set up the SSL tunnel with squid after CONNECT call succeeds. I remember
that HAProxy will send PROXY protocol line during ssl negotiation. If squid
does not parse the PROXY protocol header during SSL negotiation, this will
c
Hello-
I'm using squid version 3.5.3 and I could use some help with
configuration.
Squid will be installed at AWS, most clients will be within a corporate
network and will not be able to access the service by configuring proxy
settings in a browser. Instead DNS will be used to resolve to th
On 14/04/2015 11:57 p.m., Abdelouahed Haitoute wrote:
>
> There are two thing I haven’t realized in the development
> environment, because I don’t know how:
> 1. Making the Squid 3.1.10 to use a proxy system, because that’s our
> policy to communicate to the outside world. In apache we use the
>
On 15/04/2015 1:34 a.m., Baird, Josh wrote:
> Hi,
>
> We recently started having problems where our Squid 2.6
> (squid-2.6.STABLE21-6.el5) proxy servers would stop serving requests. In my
> cache.log, I see many of these:
>
> 2015/04/14 01:13:45| Failure Ratio at 26.15
> 2015/04/14 01:13:45| G
Hi,
We recently started having problems where our Squid 2.6
(squid-2.6.STABLE21-6.el5) proxy servers would stop serving requests. In my
cache.log, I see many of these:
2015/04/14 01:13:45| Failure Ratio at 26.15
2015/04/14 01:13:45| Going into hit-only-mode for 5 minutes...
2015/04/14 01:18:46
Hello,
Currently we’ve got the following situation in our production environment:
Clients —HTTP—> Apache —HTTPS TWO-WAY SSL VIA EXTERNAL PROXY —> HTTPS SERVERS
Just to be clear, the following services are used during this flow:
http client (firefox, chrome, curl, wget, etc.) —> Apache (which se
Hi guys,
I need your help for the same problem : I'm not able to strip the realm from
username and the `-r` switch doesn't achieve this...
Please help me !
Tim.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/strip-Kerberos-Realm-tp4498437p4670714.html
Sen
19 matches
Mail list logo
