On 27/09/22 02:25, Alex Rousskov wrote:
On 9/26/22 05:51, Théo BARRAGUE wrote:
entry is null so peerGetSomeNeighbor is never called
I did not check all the details, but it looks like Squid ICMP code
(ab)uses StoreEntry-linked metadata. Basic CONNECT tunnels lack
StoreEntry because they are
I will take a look, thank's for help 🙂
Regards,
Théo BARRAGUÉ
From: Alex Rousskov
Sent: Monday, September 26, 2022 3:25 PM
To: Théo BARRAGUE ;
squid-users@lists.squid-cache.org
Cc: Olivier HANESSE
Subject: Re: [squid-users] Use ICP RTT with HTTPS reques
On 9/26/22 05:51, Théo BARRAGUE wrote:
entry is null so peerGetSomeNeighbor is never called
I did not check all the details, but it looks like Squid ICMP code
(ab)uses StoreEntry-linked metadata. Basic CONNECT tunnels lack
StoreEntry because they are not reading/writing data from/to Store.
Hello,
Thank's for answer. I increased output level and get this :
2022/09/26 09:07:52.381| 44,3| peer_select.cc(163) peerSelect: CONNECT
2022/09/26 09:07:52.381| 44,3| peer_select.cc(472) peerSelectFoo: CONNECT
api.gouv.fr
2022/09/26 09:07:52.381| 44,3| peer_select.cc(485) peerSelectFoo:
peer
On 9/23/22 10:30, Théo BARRAGUE wrote:
How can I say "please, use ICP for RTT sharing like you did with
HTTP" ?
AFAICT, Squid tries to use NetDB on both HTTP and HTTPS paths, but
something probably goes wrong somewhere. The easiest way to figure this
out may be to analyze debugging cache.lo
