Hello,
I was wondering if anyone could take a look at this:
I'm running squid for rather long time, recently I have upgraded my squid box
to Debian 10 (from Debian 9) and OpenSSL 1.1.1d
4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
OpenSSL 1.1.1d 10 Sep 2019
s
> That is somewhat useful. TLS version being received is not valid.
Ok - although this is squid users phorum - this could be even more useful:
Firefox - http://download.kjj.cz/pub/ssl/firefox.txt it goes throught
everything to the GET / HTTP/1.1 request
Chrome - http://download.kjj.cz/pub/ssl/
ot calling parser to ask for TLS version for "random" numbers.
LL
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Loučanský Lukáš
Sent: Wednesday, June 17, 2020 9:11 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [
This is the most naïve and dirtiest effort but I don't know where else it's
called - not going to check it and fix calling it with nonsense numbers - so I
went like this:
/// parse TLS ProtocolVersion (uint16) and convert it to AnyP::ProtocolVersion
static AnyP::ProtocolVersion
ParseProtocolVers
Just noticed that github version of HandShake.cc is much better "patched" than
my humble,pitty attempt to quick-fix the parser. So in the light of self
investigation and the lack of information and experience (I'm sorry for that) I
maybe over-reacted. But now it seems both modifications made i
Sorry - but how is your solution different from:
1) openssl dhparam -outform PEM -out dhparam.pem 2048
2) https_port 3128 ssl-bump generate-host-certificates=on
dynamic_cert_mem_cache_size=4MB cert=/usr/local/squid/etc/rootCA.crt
key=/usr/local/squid/etc/rootCA.key options=SINGLE_DH_USE,SINGLE_E
Hello,
I was going to run ./configure and make all for a freshly downloaded Squid 5.1
on my current Squid 4.x rig, which so far goes all right with Squid 4.x. The
configure script went without errors, but make all stops on the missing tests
directory in the src/icmp, src/tools and src/tools/squ
Hello,
just rolled out squid 5.1 into production machine and got several of
2021/08/11 08:10:45 kid2| BUG: missing ENTRY_REQUIRES_COLLAPSING for
e:tr4315=V/0x556f34ceba10*0
current master transaction: master55
2021/08/11 08:10:48 kid2| BUG: missing ENTRY_REQUIRES_COLLAPSING for
e:tr4315=V/0
Hi,
recently I'm facing too many ERROR: Collapsed forwarding queue overflow for
kid2 at 1024 items lines in my Squid 5.2 log files. So far I was able to find
it in the CollapsedForwarding.cc func Broadcast as a result of a full queue
which limits beeing defined by the QueueCapacity const at 1024
eset in the
storeid_rewrite patterns.
LL
-Original Message-
From: Alex Rousskov [mailto:rouss...@measurement-factory.com]
Sent: Monday, November 15, 2021 5:17 PM
To: Squid Users
Cc: Loučanský Lukáš
Subject: Re: [squid-users] Too many ERROR: Collapsed forwarding queue overflow
for kid2
ot;
(no config changes)
My 1w cache.log is about 300MB - without elevated debug options (debug options
ALL,1) - so it’s not easy to find something relevant with "9" options enabled...
LL
-Original Message-
From: Alex Rousskov [mailto:rouss...@measurement-factory.com]
Sen
ushIndex: 25132, other:
25132 }
} by kid6
Seems like a new item in the cachemgr.cgi menu...
LL
-Původní zpráva-
Od: Alex Rousskov [mailto:rouss...@measurement-factory.com]
Odesláno: út 16.11.2021 19:09
Komu: Loučanský Lukáš; Squid Users
Předmět: Re: [squid-users] Too many ERROR: Colla
11/22 08:51:48 kid1| assertion failed: store.cc:1094: "store_status ==
STORE_PENDING"
(maybe consequence of too generous max-swap-rate)
LL
-Original Message-
From: Alex Rousskov [mailto:rouss...@measurement-factory.com]
Sent: Sunday, November 21, 2021 8:28 PM
To: Loučanský
why it's filling. So far I've recompiled squid with disabled
optimizations and enabled backtraces - let's see what it does while it crashes
again
LL
-Original Message-
From: Alex Rousskov [mailto:rouss...@measurement-factory.com]
Sent: Monday, November 22, 2021 5:35 PM
Hello,
as I was going through some upgrades during my investigation of the "transient"
queues overflows - I've noticed that my squid asserted on store.cc line 1094
which I read as a test to see if the store is in progress while the transfer is
being aborted. Sure enough I've found aborted reques
Hello,
my squid 5.3 with 957 patch runs for 6 days now - so everything seems ok.
Maximum Resident Size: 3798688 KB
Memory accounted for:
Total accounted: 326687 KB
But - I'd like to ask if I'm doing anything wrong. Am I correct when I think,
that patch #957 is not backport
Hello, today I was going to compile a new version of my beloved squid
proxy (v6.3 or 6.3-20230903-ra9c06aa6a) just to be welcomed by non
working older configmgr.cgi and [debian package installed] squidclient
(v4.6). After replacing squidclient with (compiled with squid) version
6.3 it's still n
arch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Th
(70) ~SBuf: SBuf15514955 destructed
BTW debug 24,9 makes pretty big log files... :-)
L
-Původní zpráva-
Od: squid-users za uživatele Loučanský Lukáš
Odesláno: út 12.9.2023 18:23
Komu: squid-users@lists.squid-cache.org
Předmět: Re: [squid-users] Squid BUG: assurance failed:
-
Od: squid-users za uživatele Alex Rousskov
Odesláno: út 12.9.2023 19:28
Komu: squid-users@lists.squid-cache.org
Předmět: Re: [squid-users] Squid BUG: assurance failed:
tok.skip(WellKnownUrlPathPrefix())
On 2023-09-12 13:06, Loučanský Lukáš wrote:
> Is this anyhow interesting?
Not really,
Od: squid-users za uživatele Alex Rousskov
Odesláno: st 13.9.2023 20:53
Komu: squid-users@lists.squid-cache.org
Předmět: Re: [squid-users] Squid BUG: assurance failed:
tok.skip(WellKnownUrlPathPrefix())
On 2023-09-12 15:50, Loučanský Lukáš wrote:
> 2023/09/12 19:12:03 kid4| ERROR:
-cache.org
Předmět: Re: [squid-users] Squid BUG: assurance failed:
tok.skip(WellKnownUrlPathPrefix())
On 15/09/23 09:55, Alex Rousskov wrote:
> On 2023-09-14 06:40, Loučanský Lukáš wrote:
>
>> But - could someone (or you) clarify the next one for me? I've read
>> some que
Hello,
this has recently started me up more then let it go. For a while chrome
is upgrading in-page links to https. It is supposed to work something
like
https://www.bleepingcomputer.com/news/google/google-chrome-now-auto-upgrades-to-secure-connections-for-all-users/
But there is a catch for
e they are
getting is not a result of a faulty local gear - nor an attempt of the
admin to spy on them or to block some sites etc.
LL
Dne 03.04.2024 v 8:14 Loučanský Lukáš napsal(a):
Hello,
this has recently started me up more then let it go. For a while
chrome is upgrading in-page links to
al(a):
On 2024-04-03 02:14, Loučanský Lukáš wrote:
this has recently started me up more then let it go. For a while
chrome is upgrading in-page links to https.
Just to add two more pieces of related information to this thread:
Some Squid admins report that their v6-based code does not suffer from
25 matches
Mail list logo
