So I got squid to intercept http and https traffic, but I get the
following error on any https access
2015/02/23 12:50:15 kid1| clientNegotiateSSL: Error negotiating SSL
connection o
n FD 28: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown
ca (1/0
)
This of course leads to
Is there a way to build 3.5.1 without libcom_err?
On my old Redhat system (2.6.18-128.1.1.el5) I get compilation failures unless
I remove all references to libcom_err.
Here's a snippet from the config log:
configure:24277: checking for krb5.h
configure:24277: result: yes
configure:24277:
there is a way without using ssl_bump
without forwarding https
but this will work with browsers and not with youtube mobile app.
its in header replace
--
View this message in context:
I'm trying to POST large files (1MB) through a squid 3.5.2 proxy set up to
intercept connections.
The client is including an 'Expect: 100-continue' header, and sends all headers
in a single network packet.
POSTs of content smaller than 1MB go through, but larger POSTs do not.
The client's TCP
i did that with version 3.5.1
now wen upgrade again for 3.5.2 my cache damaged again !!
i just want to know how this version is stable !!
its full of bugs !!
cache.log =
2015/02/23 19:20:51 kid1| Could not parse headers from on disk object
2015/02/23 19:20:51 kid1| BUG 3279: HTTP reply without
On 24/02/2015 00:53, HackXBack wrote:
there is a way without using ssl_bump
without forwarding https
but this will work with browsers and not with youtube mobile app.
its in header replace
Hey HackXBack,
I am not to familiar with all of the mobile apps but if the client needs
filtering he
Thanks for the help!
In file client_side.h:
inline void setServerBump(Ssl::ServerBump *srvBump) {
if (!sslServerBump)
sslServerBump = srvBump;
else
assert(sslServerBump == srvBump);
}
Changed to:
inline void setServerBump(Ssl::ServerBump
This is kind of off-topic but on one of our deployments this crash is now
consistently deadlocking squid whenever it occurs rather than just ending the
process. Meaning that is can’t be restarted by any means except kill -9, which
obviously a huge disruption to hundreds of clients and
On 24/02/2015 02:16, HackXBack wrote:
i did that with version 3.5.1
now wen upgrade again for 3.5.2 my cache damaged again !!
i just want to know how this version is stable !!
its full of bugs !!
Hey HackXBack,
Some would imagine that squid is perfect and if you will look at the
Bugzilla
