> On 23 Apr 2015, at 4:21 pm, Amos Jeffries wrote:
>
> On 23/04/2015 6:29 p.m., Michael Hendrie wrote:
>> Hi All
>>
>> I’ve been running squid-3.4.x in tproxy mode with ssl_bump
>> server-first for some time and has been working great.
>>
>> I have just moved to 3.5.3 to use peek to overcome s
On 23/04/2015 6:29 p.m., Michael Hendrie wrote:
> Hi All
>
> I’ve been running squid-3.4.x in tproxy mode with ssl_bump
> server-first for some time and has been working great.
>
> I have just moved to 3.5.3 to use peek to overcome some issues with
> sites that require SNI to serve up the correct
Hi All
I’ve been running squid-3.4.x in tproxy mode with ssl_bump server-first for
some time and has been working great.
I have just moved to 3.5.3 to use peek to overcome some issues with sites that
require SNI to serve up the correct certificate. In most cases this is work
well however I se
On 23/04/2015 5:10 p.m., Victor Sudakov wrote:
> Dear Colleagues,
>
> I have two squid-3.5.3 proxies configured as mutual siblings:
>
> proxy:/usr/local/etc/squid/squid.conf
>
> acl internal src 212.73.124.0/28
> http_access allow internal
> cache_peer proxy2.sibptus.ru sibling 3128 3130
>
On 23/04/2015 9:14 a.m., Nick Rogers wrote:
> After upgrading from 3.4.x to 3.5.x, I've noticed a new error message with
> my squid configuration. Apparently squid 3.5 no longer allows setting the
> two lower-most ECN bits of the ToS byte.
Allowing it and leaving it up to admin was causing too muc
Dear Colleagues,
I have two squid-3.5.3 proxies configured as mutual siblings:
proxy:/usr/local/etc/squid/squid.conf
acl internal src 212.73.124.0/28
http_access allow internal
cache_peer proxy2.sibptus.ru sibling 3128 3130
proxy2:/usr/local/etc/squid/squid.conf
acl cisa_servers src
Here it's working fine in both intercept,tproxy and forward proxy mode.
What version are you using?
What OS?
Did you had the chance to see some access.log output??
Eliezer
* This is one of the days we can say thanks for the first squid
developers which helped us with this great piece of softwar
root@issa:~# netstat -anl | grep 80 | awk '/^tcp/ {t[$NF]++}END{for(state in
t){print state, t[state]} }'
FIN_WAIT2 12
LISTEN 1
CLOSE_WAIT 3
TIME_WAIT 809
ESTABLISHED 597
LAST_ACK 9
SYN_SENT 4
FIN_WAIT1 14
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/asse
root@fibernet:~# netstat -anl | grep 80 | awk '/^tcp/ {t[$NF]++}END{for(state
in t){print state, t[state]} }'
FIN_WAIT2 1
LISTEN 1
CLOSE_WAIT 7
TIME_WAIT 71
ESTABLISHED 125
LAST_ACK 2
FIN_WAIT1 2
Every 2.0s: netstat -antop | grep -iE --regexp="TIME_WAIT"
after discussing this with Yuri we have thinking is the problem in
close-wait connections,
i try to put half_closed_clients off
but this didnt solve the problem
some thing here make this assertion error since it not happen immediately ,
some times every 20 min and some times it need 5 hours to exi
After upgrading from 3.4.x to 3.5.x, I've noticed a new error message with
my squid configuration. Apparently squid 3.5 no longer allows setting the
two lower-most ECN bits of the ToS byte. I realize that this is to
encourage people to use the modernized definition of ToS being a 6 bit DSCP
field a
no one can find solution for this issue ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670726p4670868.html
Sent from the Squid - Users mailing list archive at Nabble.com.
__
Clients must also be pointed to these DNS IP.
22.04.15 10:18, Hierony Manurung пишет:
Hierony Manurung
Del Institute of Technology
Network Management
Pada Rabu, 22 April 2015 10:53,
"squid-users-ow...@lists.squid-cache.org"
menulis:
- Pesan yang Diteruskan -
You are not allowed
13 matches
Mail list logo
