On 14/06/2016 1:06 p.m., Eliezer Croitoru wrote:
> Hey Amos,
>
> I have just released the latest 4.0.11 beta RPMs for:
> - CentOS 7
> - Oracle Linux 7
> - SLES 12SP1
> - OpenSUSE leap
> (all for x86_64 only)
> I started testing on CentOS 7 and until now I do not see any visible
> regression.
>
On 13.06.16 14:29, Jaap Dam wrote:
I've got a reliable but slow backend that sends cacheble responses. When I
run a manual test, I can see I miss the cache every one in a while and got
hits most of the time. This is also reflected in the response time, 200+ ms
for a miss, ~20ms for a hit.
how d
On 14/06/2016 12:29 a.m., Jaap Dam wrote:
> Is the collapsed_forwarding directive the correct one to use for my
> use-case or am i missing something?
Yes it is correct so far as I am understanding your need.
For further debugging about what is going on you will need the HTTP
messages involved. Ad
On Monday 13 June 2016 at 15:01:02, Nilesh Gavali wrote:
> Facing issue while accessing HTTPS via squid, normal http traffic working
> fine.
Please define "issue", with as much detail as possible:
- what exactly are you trying to do when a problem occurs?
- have you previously been able to do
Hello All;
Facing issue while accessing HTTPS via squid, normal http traffic working
fine. I have squid 3.1.10 on RHEL.6.0
attached is my squid .conf for your reference,..help will be much
appreciated.
Thanks & Regards
Nilesh Suresh Gavali
=-=-=
Notice: The information con
Hi,
I've got a reliable but slow backend that sends cacheble responses. When I
run a manual test, I can see I miss the cache every one in a while and got
hits most of the time. This is also reflected in the response time, 200+ ms
for a miss, ~20ms for a hit.
However when I request the same resour
On 6/06/2016 11:23 p.m., FredB wrote:
>
> Capture with swap full
>
> total used free sharedbuffers cached
> Mem:63 62 0 0 2 19
> -/+ buffers/cache: 40 22
> Swap:1 1
On Monday 13 June 2016 at 12:55:43, Yuri Voinov wrote:
> Yes no problem. Signs the certificate of the local web server with root
> certificate the proxy, which is already in user's browser - and voila.
True - or at least it would be if the OP hadn't said "Using the certificate is
something I wan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yes no problem. Signs the certificate of the local web server with root
certificate the proxy, which is already in user's browser - and voila.
13.06.2016 15:01, Antony Stone пишет:
> On Monday 13 June 2016 at 10:51:35, Eng Hooda wrote:
>
>> Thank
On Monday 06 June 2016 at 13:23:17, FredB wrote:
> Capture with swap full
> Tasks: 2740 total, 3 running, 2737 sleeping, 0 stopped, 0 zombie
Hm, isn't 2740 tasks rather a lot? What are most of them? With a load
average of 0.81 it looks like maybe you have a very large number of child
process
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-4.0.11 release!
This release is a bug fix release resolving several issues found in the
prior Squid releases.
The major changes to be aware of:
* HTTP/1.1: unfold mime header block
HTTP/1.0 allowed headers to
Thank You Amos Jeffries & Eliezer Croitoru
Issue was resolved.
Here is how it's was resolved FYI.
I installed pdns_recursor and redirected all DNS queries to it.
But it didn't work directly , I have a MikroTik router in the path to squid
that I discovered it replies to DNS queries even when all
On Monday 13 June 2016 at 10:51:35, Eng Hooda wrote:
> Thank You for your response.
> Using the certificate is something I want to avoid.
> So I think it's acceptable as it is now.
>
> I searched again and found an explanation , copied below FYI.
>
> "To serve an HTTP error to an SSL client, Squ
Thank You for your response.
Using the certificate is something I want to avoid.
So I think it's acceptable as it is now.
I searched again and found an explanation , copied below FYI.
"
To serve an HTTP error to an SSL client, Squid has to establish an SSL
connection with that client.
"
On
14 matches
Mail list logo
