Dear all,
As I was playing around with Squid and e-cap, I decided to shutdown squid,
clear the cache and the log files.
Now, when I start it, it seems to create both the access.log and cache.log
files, but it only writes to the cache.log file:
root@appliance:/var/log/squid3# ls -al
total 16
drwxr
Hi All,
I am trying to configure an intercept proxy with peek/splice/terminate features
in Squid 3.5.1 on CentOS 7 - 64 bit. I wanted to peak at steps 1 and step 2 and
to decide on terminate on step 3 based on the SNI and server certificate
values. It is working only for https://www.google.com,
On Fri, Feb 13, 2015 at 02:44:14PM +0600, Yuri Voinov wrote:
>
> In addition, the operating system with a constant load of RAM in the
> 90-95% is just on the edge of a swap or a kernel panic. For Solaris this
> is not care - but it has a very specific kernel. Most of the other OS
> just goes to
Hi guys,
I'm using squid-3.4.8 in my box running on Linux platform. I
want to syslog the access_log to remote server.
But I don't see any logs on remote server when I use 'NOTICE' priority in my
config file. Below is my config file.
http_port 3128 transparent
access_log syslog:local7.
Hi Amos,
Thank you for your reply.
The information I need to apply to the header is client specific, ex their
internal ip address.
The issue I am facing is that the network that is hosting the web services
is different from the network that the clients are accessing it from. So my
Squid instance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/02/2015 11:46 a.m., Yuri Voinov wrote:
>
>
> 16.02.15 4:40, James Beecham пишет:
>> Hi Yuri,
>
>> Thank you.
>
>> Are these HTTPS CONNECT requests coming over port 80? If not
>> would I need
>
> It depends. In different configurations uses d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
16.02.15 4:40, James Beecham пишет:
> Hi Yuri,
>
> Thank you.
>
> Are these HTTPS CONNECT requests coming over port 80? If not would
> I need
It depends. In different configurations uses different ports. In
transparent interception mode your absol
Hi Yuri,
Thank you.
Are these HTTPS CONNECT requests coming over port 80? If not would I need
to make a rule to forward 443 to another Squid port configured to ssl_bump?
James
On Sun, Feb 15, 2015 at 2:37 PM, Yuri Voinov wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> http://wiki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And here
http://wiki.squid-cache.org/ConfigExamples/Intercept/SslBumpExplicit
16.02.15 3:49, Eliezer Croitoru пишет:
> On 15/02/2015 23:36, Alan Palmer wrote:
>> I'm trying to get squid 3.4.11 on openbsd 5.6 to act as a
>> transparent ssl proxy.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://wiki.squid-cache.org/ConfigExamples/Intercept/SslBumpExplicit
16.02.15 4:02, James Beecham пишет:
> Hello,
>
> Thank you to everyone who works on this great project! I have been
> using Squid as an intercept for a while now and am very happy.
Hello,
Thank you to everyone who works on this great project! I have been using
Squid as an intercept for a while now and am very happy.
I have a high level question regarding SSL_Bump.
My company recently switched to using SSL for our web services, which
requires me to make some changes to the
On 15/02/2015 23:36, Alan Palmer wrote:
I'm trying to get squid 3.4.11 on openbsd 5.6 to act as a transparent
ssl proxy.
I've rebuilt squid with --enable-ssl-crtd, generated my own self signed
cert (ala http://www.akadia.com/services/ssh_test_certificate.html) and
have the following config lines
I'm trying to get squid 3.4.11 on openbsd 5.6 to act as a transparent
ssl proxy.
I've rebuilt squid with --enable-ssl-crtd, generated my own self signed
cert (ala http://www.akadia.com/services/ssh_test_certificate.html) and
have the following config lines:
https_port 3127 transparent ssl-bu
On 16/02/2015 8:41 a.m., Mohammad Shakir wrote:
> We are using squid 3.4.9 on centos 64bit and getting following error.
>
>
> assertion failed: filemap.cc:72: "capacity_ <= (1 << 24)"
This is http://bugs.squid-cache.org/show_bug.cgi?id=3566
The filemap is a 24-bit map value used to represent t
We are using squid 3.4.9 on centos 64bit and getting following error.
assertion failed: filemap.cc:72: "capacity_ <= (1 << 24)"
In cache directory swap.state file size is.
-rw-r- 1 squid squid 1.2G Feb 16 00:15 swap.state
Should we upgrade to new version to resolve this issue ?
Squid
assertion failed: comm.cc:769: "Comm::IsConnOpen(conn)"
every few hours i got this error this squid restart automatically
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-769-Comm-IsConnOpen-conn-tp4669842.html
Sent from the Squid -
16 matches
Mail list logo
