Further to this on running squidclient mgr:info
I always get:
Maximum number of file descriptors: 16384
be it after start or after reload OR even if i mention max_filedescriptor 1024
or 4096.
looks like somewhere this number 16384 is hard-coded in 3.3.0.1
Amm
- Original Message
Ok, I will try!
One last question because it is not so clear yet.
WHY when I set up Squid as I done http_port 3128 and http_port 3129 tproxy,
using the routing table of the site, I can't access the Apache web server in
the same machine?
If I send a request to the [4001::52] (with Apache and
On 24/10/2012 10:53 p.m., alberto.desi wrote:
Ok, I will try!
One last question because it is not so clear yet.
WHY when I set up Squid as I done http_port 3128 and http_port 3129 tproxy,
using the routing table of the site, I can't access the Apache web server in
the same machine?
If I send a
On 24/10/2012 8:00 p.m., Amm wrote:
Further to this on running squidclient mgr:info
I always get:
Maximum number of file descriptors: 16384
be it after start or after reload OR even if i mention max_filedescriptor 1024
or 4096.
looks like somewhere this number 16384 is hard-coded in
Hi,
My squid 3.2.2 - R is failing after a reconfigure.
Not using SMP.
here is what I find in the logs :
2012/10/24 14:54:42 kid1| assertion failed: comm.cc:163:
!fd_table[conn-fd].closing()
2012/10/24 14:58:29 kid1| StoreEntry-ping_status: 2
2012/10/24 14:58:29 kid1|
Hi,
I'm sorry if this sounds trivial.
I've read the documentation on transporting traffics, but it seems
that I still have no luck
transporting traffics through multiple IPv6 addresses.
Note that I setup transporting with IPv4 without problem. So I wonder
if there's anything
I've missed in my
Ah yes, you are right. I just checked the spec file
--with-filedescriptors=16384
Earlier I didnt check spec file because EXACTLY same spec file was used for
3.2.1 and it was using max_filedescriptor setting even when compile time 16384
was mentioned. Its strange though.
Anyway atleast
For future reference, I believe the problem I described was fixed sometime
between 3.1.19 and the current 3.2.3. I just pulled down the source to
3.2.3 and ran it with my exact same url_rewrite_program and I no longer have
any problems with URL parameters. Everything works as I would have
On 25.10.2012 05:44, Welly Hartanto wrote:
Hi,
I'm sorry if this sounds trivial.
I've read the documentation on transporting traffics, but it seems
that I still have no luck
transporting traffics through multiple IPv6 addresses.
Note that I setup transporting with IPv4 without problem. So I
Hello,
Can squid working as a forward proxy and using client cert? If a user
imported the own certificate file to a browser can the squid request
and check it? If the client cert is present the user allow to use the
squid forward proxy. (Not reverse) Thank you for your help.
On 25/10/2012 1:54 p.m., Jeszenszky Zoltán wrote:
Hello,
Can squid working as a forward proxy and using client cert? If a user
imported the own certificate file to a browser can the squid request
and check it? If the client cert is present the user allow to use the
squid forward proxy. (Not
11 matches
Mail list logo
