Hello!
I would like to switch from SLES to CentOS Squid proxy server and just
learned that icap is no longer up-to-date.
Better use eCap, but i am not able to find a good howto telling me how
to get it to work in my environment.
Can anybody help me out ?
Thanks, Björn.
Träger: Klinikum
On 20/12/2016 9:52 a.m., Sameh Onaissi wrote:
>
>> On Dec 19, 2016, at 1:31 PM, Antony Stone wrote:
>>
>> On Monday 19 December 2016 at 17:44:11, Sameh Onaissi wrote:
>>
>>> Hello,
>>>
>>> I was using squid client to get cache stats, however this morning it
>>> completely stopped working.
>>
>>>
On Sun, Dec 18, 2016, at 11:24 PM, Amos Jeffries wrote:
> On 19/12/2016 5:59 p.m., creditu wrote:
> >
> > On Sun, Dec 18, 2016, at 01:21 PM, Michael Pelletier wrote:
> >> Check your file permissions on the key.
> >>
> >> On Dec 18, 2016 2:13 PM, creditu wrote:
> >>
> >>> I'm having trouble
> On Dec 19, 2016, at 1:31 PM, Antony Stone
> wrote:
>
> On Monday 19 December 2016 at 17:44:11, Sameh Onaissi wrote:
>
>> Hello,
>>
>> I was using squid client to get cache stats, however this morning it
>> completely stopped working.
>
>>
On Monday 19 December 2016 at 17:44:11, Sameh Onaissi wrote:
> Hello,
>
> I was using squid client to get cache stats, however this morning it
> completely stopped working.
> http://mydomainname.com/squid/access_denied.jpg;
> alt="Acceso Denegado" style="width:704px;height:428px;">
> the html
The site I was having trouble with was video.foxnews.com. The page loads
but the actual video hangs with "spinning wheel of death". I took Amos
suggestion and added deny via, request-x-forward and that fixed the issue
but I was trying to create the anonymous proxy paranoid setup initially,
and
On 12/19/2016 09:44 AM, Sameh Onaissi wrote:
> squid client returns numbers based on traffic on 3128 by default right?
No, the above statement is incorrect. The cache manager interface
reports whole-Squid statistics by default, including all listening ports.
Alex.
Hello,
I was using squid client to get cache stats, however this morning it completely
stopped working.
When I run squidclient mgr:info I get the following
HTTP/1.1 200 OK
Date: Mon, 19 Dec 2016 16:33:44 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Fri, 25 Nov 2016 16:55:22 GMT
ETag:
Hello,
I was using squid client to get cache stats, however this morning it completely
stopped working.
When I run squidclient mgr:info I get the following
HTTP/1.1 200 OK
Date: Mon, 19 Dec 2016 16:33:44 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Fri, 25 Nov 2016 16:55:22 GMT
ETag:
On 19 December 2016 at 16:06, Eliezer Croitoru wrote:
> Did you noticed these errors:
> FATAL: The ssl_crtd helpers are crashing too rapidly, need help!
>
> Squid Cache (Version 3.5.23): Terminated abnormally.
> CPU Usage: 63.837 seconds = 28.308 user + 35.529 sys
> Maximum
On 20/12/2016 2:06 a.m., Eliezer Croitoru wrote:
> Did you noticed these errors:
> FATAL: The ssl_crtd helpers are crashing too rapidly, need help!
>
Unfortunately that helper does not have much debug to figure out why its
crashing. There are a couple of bug reports open about this crashing,
but
Hi guys, have been getting crashes with this message..
2016/12/19 10:00:06 kid1| assertion failed: client_side_reply.cc:1167:
"http->storeEntry()->objectLen() >= headers_sz"
clean rockstore databases from 3 days ago
cache_dir rock /cache 135000 min-size=0 max-size=12288 slot-size=12288
Based on Amos's Answer,
acl serverIsws ssl::server_name .w0.whatsapp.com
acl serverIsws ssl::server_name .w1.whatsapp.com
acl step1 at_step SslBump1
ssl_bump peek step1
ssl_bump bump !serverIsws all
ssl_bump splice all
will above work ?
Or should i splice first and bump all others later?
This
I can give a hint that once you see the request you can identify using an
ICAP\ECAP services couple details about the request.
Basically I had a regex which allowed any what's app traffic to be spliced by
the SNI domain name.
It should be something like "w[0-9]+\.web\.whatsapp\.com$" to match
Did you noticed these errors:
FATAL: The ssl_crtd helpers are crashing too rapidly, need help!
Squid Cache (Version 3.5.23): Terminated abnormally.
CPU Usage: 63.837 seconds = 28.308 user + 35.529 sys
Maximum Resident Size: 171488 KB
Page faults with physical i/o: 154
2016/12/18 17:25:05| Set
On 20/12/2016 12:44 a.m., David Touzeau wrote:
>
> Hi
>
> Squid accept "Proxy protocol" in http_port, is there a chance to see "PROXY
> Protocol" supported in cache_peer if you need to link 2 squid ?
>
'a chance' only at this point unless somebody (you?) wants to sponsor
it. It is on my TODO
Oh sorry, I miss some replys.
>I think you still have a forwarding loop. Does the cisco WCCP send port
>443 connections from Squid to reach the Internet instead of sending them
>back into Squid.
interface TenGigabitEthernet0/2/0.501
description for WCCP
encapsulation dot1Q 501
ip address
Hi
Squid accept "Proxy protocol" in http_port, is there a chance to see "PROXY
Protocol" supported in cache_peer if you need to link 2 squid ?
Best regards.
___
squid-users mailing list
squid-users@lists.squid-cache.org
Hi,
I have added details.txt and also fixed perms on cache.log
On 19 December 2016 at 14:10, Eliezer Croitoru wrote:
> The file:
> http://gw.crownkenya.com/~wash/3.5.22/cache.log.txt
>
> isn't accessible.
> Also missing details like OS version and other things.
> It seems
19 matches
Mail list logo