Re: [squid-users] squid 3.5.5 issue after restart the system

I checked my email which show me that my email address has been blocked by squid-user list so I could not check it. Now should I upgrade to higher version ? On Tuesday, June 30, 2015 9:38 AM, Amos Jeffries wrote: On 30/06/2015 4:24 p.m., Mohammad Shakir wrote: > We are using squid on cento

Re: [squid-users] sslbump and caching of generated cert

On 30/06/2015 5:35 a.m., Alex Wu wrote: > So far as I know, hen sslbump is enabled for a port, for each dns > name, squid save a cert generated according to dns name and signing > key (from http_port configuration). So the next time, the generated > cert can be fetched if the same dns host and conf

Re: [squid-users] squid 3.5.5 issue after restart the system

On 30/06/2015 4:24 p.m., Mohammad Shakir wrote: > We are using squid on centon 6.6 64 bit with this option. > Did you see the responses to your post from yesterday? Amos ___ squid-users mailing list

Re: [squid-users] tcp_outgoing_address binds to wrong interface

On 30/06/2015 8:54 a.m., Nick Rogers wrote: > Hello, > > I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where > tcp_outgoing_address correctly rewrites the source address of outgoing > packets, but fails to bind the socket to the correct interface. I've been > using this kind of setu

[squid-users] squid 3.5.5 issue after restart the system

We are using squid on centon 6.6 64 bit with this option. Squid Cache: Version 3.5.5 Service Name: squid configure options: '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/sbin' '--sbindir=/usr/sbin' '--sysconfdir=/etc/squid' '--datadir=/usr/share/squid' '--includedir=/usr/include' '--libdi

[squid-users] tcp_outgoing_address binds to wrong interface

Hello, I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where tcp_outgoing_address correctly rewrites the source address of outgoing packets, but fails to bind the socket to the correct interface. I've been using this kind of setup/configuration for quite some time (since the squid 2.7

[squid-users] sslbump and caching of generated cert

So far as I know, hen sslbump is enabled for a port, for each dns name, squid save a cert generated according to dns name and signing key (from http_port configuration). So the next time, the generated cert can be fetched if the same dns host and configured signing key. Now have a question on t

Re: [squid-users] TCP_MISS/504 in cache_peer

On 30/06/2015 12:50 a.m., Stakres wrote: > Hi Amos, > > 1. What does the 504 mean ? One of the proxies timed out while contacting the origin server, OR the origin server acting as a gateway to a CGI backend timed out waiting for the object to b

Re: [squid-users] TCP_MISS/504 in cache_peer

Hi Amos, 1. What does the 504 mean ? 2. How can i extend the TTL transaction ? Thanks :o) -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-MISS-504-in-cache-peer-tp4671944p4671946.html Sent from the Squid - Users mailing list archive at Nabble.com. _

Re: [squid-users] TCP_MISS/504 in cache_peer

On 30/06/2015 12:34 a.m., Stakres wrote: > Hi All, > is someone with an idea why it happens ? > *TCP_MISS/504 708 GET http://www.myexamplecom/images/menu_hover_left.png - > CD_SIBLING_HIT/x.x.x.x* > > i can see the TCP_MISS with the SIBLING only... > i'm looking for this issue since several days a

[squid-users] TCP_MISS/504 in cache_peer

Hi All, is someone with an idea why it happens ? *TCP_MISS/504 708 GET http://www.myexamplecom/images/menu_hover_left.png - CD_SIBLING_HIT/x.x.x.x* i can see the TCP_MISS with the SIBLING only... i'm looking for this issue since several days and it makes me crazy thanks in advance. bye Fred -

Re: [squid-users] assertion failed: comm.cc:178: "fd_table[conn->fd].halfClosedReader != NULL"

On 29/06/2015 10:56 p.m., HackXBack wrote: > i gave you backtrace report and i gave you my configure option ? > what else you want from me ? The backtrace shows where the assert is from. But without those symbols the gdb cant seem to find in your builds we cant debug what state the transaction is

Re: [squid-users] assertion failed: comm.cc:178: "fd_table[conn->fd].halfClosedReader != NULL"

i gave you backtrace report and i gave you my configure option ? what else you want from me ? when i use youtube mobile app that its content is 206 , then the server crashed immediately ... this problem need to be solved, am ready for any info's you need. Thanks -- View this message in context:

Re: [squid-users] Strange warning - squid 3.0

Means exactly your seen. You acl contains two lines with this subnetwork. Check and correct. 29.06.15 14:55, Fiorenza Meini пишет: Hi, I see this error when I restart squid service: please, what does it mean: WARNING: because of this '192.168.100.164' is ignored to keep splay tree searching p

Re: [squid-users] Strange warning - squid 3.0

On Monday 29 Jun 2015 at 09:55, Fiorenza Meini wrote: > Hi, > I see this error when I restart squid service: > > please, what does it mean: > WARNING: because of this '192.168.100.164' is ignored to keep splay tree > searching predictable ? It means that squid is going to ignore the address 192.

[squid-users] Strange warning - squid 3.0

Hi, I see this error when I restart squid service: please, what does it mean: WARNING: because of this '192.168.100.164' is ignored to keep splay tree searching predictable ? Below there is the warning that is reported Shutting down WWW-proxy squid 2015/06/29 09:19:10| WARNING: '192.168.100.