Thanks for the explanation.
From your first email :
>> "In normal operation it is not serious, but you are already into abnormal
>> operation by the crashing. So not releasing sockets/FD fast enough makes the
>> overall problem worse."
I see that all the relevant FDs are opened by squid-1 proces
I have just checked with the debug_options and saw that
sslflags=DELAYED_AUTH made it skip the client cert request. Just commented
that on the config and now it works!
Thanks a lot!
Amos Jeffries , 19 Tem 2018 Per, 11:35 tarihinde şunu
yazdı:
> On 18/07/18 23:54, login mogin wrote:
> > Hi there,
Hi Guys,
I've run into an issue with proxy and FTP. Squid is doing more than a browser
would do to display a directory listing but I'm not sure why.
The FTP site has a directory structure like /top/dir1/dir2/dir3/files where
dir2 is not readable. Using a browser without proxy, you can navigate to
On 07/19/2018 12:08 PM, Eliezer Croitoru wrote:
> So the ROOT CA key which squid is using is being used for all the fake
> certificates, why do we need so many copies of it?
FWIW, I cannot think of any reason to store the CA certificate key in
the database of generated certificates. That key is
If you want, please support this topic in the bug-report
http://lists.squid-cache.org/pipermail/squid-users/2018-July/018743.html
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
Thanks!
I didn't had much time to file the report due to some overload at work.
And I kind of overcome some level of this issue with a tiny ICAP REQMOD hack.
It's not the best solution but if it works and removes from the StoreID helper
the
burden to reach any form of DB like MySql or Redis or Me
Sorry a keyboard key broke while reviewing the text...
OK so it doesn't make any sense to store so many copies of the exact same "KEY"
in the ssl_db/certs files..
I took a sample from my certs directory and extracted the keys that are stored
at the QA server:
## Start
[root@squid4-testing 1]# ll
OK so it doesn't make any sense to store so many copies of the "KEY" in the
ssl_db/certs files..
I took a sample from my certs directory and extracted the keys that are stored
at
]\
[root@squid4-testing 1]# ll
total 12
-rw-r--r--. 1 root root 1704 Jul 19 20:58 key1.pem
-rw-r--r--. 1 r
On your recommendation posted it in bug-story of squid
https://bugs.squid-cache.org/show_bug.cgi?id=4873
We will wait for the release of the patch with impatience.
чт, 19 июл. 2018 г. в 17:46, Alex Rousskov :
>
> On 07/19/2018 05:58 AM, Michael Pro wrote:
> > Not only I have this problem
> > http:
On 07/19/2018 05:58 AM, Michael Pro wrote:
> Not only I have this problem
> http://lists.squid-cache.org/pipermail/squid-users/2018-July/018637.html
> Is it worthwhile in the near future to expect to fix this bug, or to
> hook, I hope temporarily, a bunch of icap-> mysql <->
> store_id_program?
I
Not only I have this problem
http://lists.squid-cache.org/pipermail/squid-users/2018-July/018637.html
Is it worthwhile in the near future to expect to fix this bug, or to
hook, I hope temporarily, a bunch of icap-> mysql <->
store_id_program?
ср, 18 июл. 2018 г. в 23:35, Alex Rousskov :
>
> On 07/1
live access.log streams is probably the most efficient way of doing this.
Concerning this moment
So in the logs only one half of the traffic, and if the incoming + outgoing
https://alter.org.ua/soft/fbsd/squid_tot_sz/
All the patches I found are related to the old versions of the SQUID
for 3.5
On 18/07/18 23:54, login mogin wrote:
> Hi there,
>
> I have just tried with the patch and it is still not working. Do you
> want any particular log or debug output?
>
If you could provide the cache.log output with:
debug_options ALL,1 3, 5, 83,9
... and a full-data packet trace of the TLS ha
13 matches
Mail list logo
