From scan-admin at coverity.com  Mon Nov  4 08:18:47 2024
From: scan-admin at coverity.com (scan-admin at coverity.com)
Date: Mon, 04 Nov 2024 08:18:47 +0000 (UTC)
Subject: Coverity Scan: Analysis completed for varnish
Message-ID: <67288366ea93e_a969f2bbe702d19a093c4@prd-scan-dashboard-0.mail>


    Your request for analysis of varnish has been completed successfully.
    The results are available at https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2BKADyCpvUKOL6EWmZljiu6BUNirv33lqHGQsDVQ-2BP2tg6QNq2-2FpfeAVxnw32Pj2zw-3D-3DRTG__yQhjbMw4LeDZMA4nqwf-2BPKRH1TcZpi4LlAZWuGRhHR3xft9zDZClCvgJBzIaqExVQAxqs6kcEmI-2B5mi-2Bb1i9crFbq8hddK6B32yh8vrZZifl4Y-2F5fu0x8chl0TqV5mSVcs45FV1vb3FZgnsXNpLFkTzoFsn6v4qJ31Hq2b-2FSt1dDnEbfwtc-2BzCDzmONT6wAlL-2FhKWd6SgVP1jXgMegRw8RtDXY1cvsd4W5Zt3ArkObc-3D

    Build ID: 651753

    Analysis Summary:
       New defects found: 0
       Defects eliminated: 0


From dridi at varni.sh  Mon Nov  4 11:24:36 2024
From: dridi at varni.sh (Dridi Boukelmoune)
Date: Mon, 4 Nov 2024 11:24:36 +0000
Subject: My varnish stash left github
Message-ID: <CABoVN9C-cqShy=J1Xo2jTbqXH3Q55C8sZ+gZxKwVvu-ygNGjYw@mail.gmail.com>

Greetings,

I'm cross-posting this short announcement on both misc and dev
lists because my projects target both developers and users.

In short, I [re]moved almost all my git repositories from github and
some of them landed on sourcehut. I grouped them under a project
I called varnish-stash even though these projects aren't related.

They relate to Varnish Cache so that ought to be enough.

In the process of moving them, I cut a maintenance release of
vmod-querystring with better packaging and the very first VCDK
release, with a working VSC template!

<insert confettis here>

https://sr.ht/~dridi/varnish-stash/sources

I have not set up anything for contributions and will wait for someone
to actually reach out to decide on how to proceed. I haven't had one
for a long time, but I took care of pending issues and pull request
before removing stuff on github.

Cheers,
Dridi

From phk at phk.freebsd.dk  Mon Nov  4 15:08:03 2024
From: phk at phk.freebsd.dk (Poul-Henning Kamp)
Date: Mon, 04 Nov 2024 15:08:03 +0000
Subject: No bugwash on 2024-11-11
Message-ID: <202411041508.4A4F8347011598@critter.freebsd.dk>

Due to travel and holidays, there will be no bugwash on November 11th.



-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

From walid.boudebouda at varnish-software.com  Fri Nov  8 08:49:35 2024
From: walid.boudebouda at varnish-software.com (Walid Boudebouda)
Date: Fri, 8 Nov 2024 09:49:35 +0100
Subject: 7.6.1 Release date
Message-ID: <CABs7ENk7w3gdjfjiufmN1EhXUBHLtuZje2-OQE0nyeQCJC2E3g@mail.gmail.com>

Hi everyone,

Just wanted to have you opinion on:
https://github.com/varnishcache/varnish-cache/pull/4225#issuecomment-2463134798

Do you think we should postpone the release to include the two items or
just skip them ?

Thanks,
Walid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20241108/f7b5703c/attachment.html>

From phk at phk.freebsd.dk  Fri Nov  8 08:57:00 2024
From: phk at phk.freebsd.dk (Poul-Henning Kamp)
Date: Fri, 08 Nov 2024 08:57:00 +0000
Subject: 7.6.1 Release date
In-Reply-To: <CABs7ENk7w3gdjfjiufmN1EhXUBHLtuZje2-OQE0nyeQCJC2E3g@mail.gmail.com>
References: <CABs7ENk7w3gdjfjiufmN1EhXUBHLtuZje2-OQE0nyeQCJC2E3g@mail.gmail.com>
Message-ID: <202411080857.4A88v0Qs006144@critter.freebsd.dk>

--------
Walid Boudebouda writes:

> Hi everyone,
>
> Just wanted to have you opinion on:
> https://github.com/varnishcache/varnish-cache/pull/4225#issuecomment-2463134798

It is not nearly important enough to become a last-second "we havn't properly tested
this" commit.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

From scan-admin at coverity.com  Mon Nov 11 08:33:49 2024
From: scan-admin at coverity.com (scan-admin at coverity.com)
Date: Mon, 11 Nov 2024 08:33:49 +0000 (UTC)
Subject: Coverity Scan: Analysis completed for varnish
Message-ID: <6731c16c4bd4f_1182782bbe702d19a09388@prd-scan-dashboard-0.mail>


    Your request for analysis of varnish has been completed successfully.
    The results are available at https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2BKADyCpvUKOL6EWmZljiu6BUNirv33lqHGQsDVQ-2BP2tg6QNq2-2FpfeAVxnw32Pj2zw-3D-3DjGq1_yQhjbMw4LeDZMA4nqwf-2BPKRH1TcZpi4LlAZWuGRhHR3FCZSbb54ri8Q-2FaSfZ2ZNeslAAUntLOSJG7c5Qhv44LRRwmB6ThRNSwZKmOjT9XxUNarD5Q63UkPNKHNTpJ-2BaNM70gEDsjiPZmZDDyNj-2BWkE5PDkRJLLaFNRNpbHMTJ2lovsPFU6NYPsYGIrf1UUH53YCDWjsT7M5ayVoNZDA9KfF-2F-2FJnAG2tQWnVAkrgXufU-3D

    Build ID: 653281

    Analysis Summary:
       New defects found: 0
       Defects eliminated: 0


From nils.goroll at uplex.de  Thu Nov 14 17:18:00 2024
From: nils.goroll at uplex.de (Nils Goroll)
Date: Thu, 14 Nov 2024 18:18:00 +0100
Subject: the http workshop 2024 is over
Message-ID: <55038113-6ae5-407a-a393-1cc235f6d116@uplex.de>

... so here is my report addition from the train, after having had to leave a 
little early.

Most of the general reporting work has already been done by the workshop's 
inofficial correspondent Daniel Stenberg, so I will link to his blog and just 
add some comments from my personal notes. I will mostly only comment where I 
believe to have anything to add, so not all the points are reflected. Read 
Daniel's blog and the slides...

DAY1
----

https://daniel.haxx.se/blog/2024/11/13/the-2024-http-workshop/

Make Cleartext HTTP harder

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/1.%20Security/cleartext.pdf

I was probably one of those "bringing back the discussion" which Daniel thought 
had been left behind, but I find the idea of a "central url registry" simply 
evil and with the increasing lock-in of user-agents, this topic felt to me like 
dialing up the frog-boiler's temperature another tick.

The valid argument behind the discussion is the need to solve the tls downgrade 
issue. HSTS only works after having visited a site at least once, so there is 
the "preload list" and sure enough, that doesn't scale. I do not have a solution 
to the problem either, but killing clear text http deployments does really not 
seem like the right choice to me - even if they are already made less and less 
attractive because of reduced support for newer browser features.

HTTP 2/3 abuses

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/1.%20Security/glitches.pdf

Read the slides! We as Varnish-Cache should really consider Willy's explicit and 
implicit advise from his experience and I expect to personally get back to this 
relatively soon, because I am getting closer to the H2 re-implementation which I 
have on my list for next year...

QUIC pacing

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/2.%20Performance/quic%20pacing.pdf

Maybe not for our immediate attention, but the insights seem very valuable. In 
particular the "send acks in intervals of rtt" advice, and I learned an 
interesting detail from side discussions: At least two people from different 
teams said that they found SO_TXTIME to be broken on Linux.

Priorities

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/2.%20Performance/HTTP%20prioritization.pdf

One interesting idea from the discussion: implement one priority as a cache 
pre-warm "fetch, but don't send at all". If the client then decides it actually 
wants the object, it updates the priority...

DSR

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/2.%20Performance/QUIC%20cache%20DSR.pdf

Discussing the topic after the workshop, I learned about one use case which was 
absolutely not clear to me: At scale, the traffic patterns can be such that it 
does not pay off to copy longtail objects to another "neighbor" cache in the 
same cluster. So yes, DSR seems to make sense. Though the particular design 
presented looked to me like there really should be an easier way...

DAY2
----

https://daniel.haxx.se/blog/2024/11/13/the-2024-workshop-day-two/

CAPSULE

This made me realize again really _how_ many not even particularly new things 
there are where we as Varnish-Cache have nothing to offer...

Reverse HTTP

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/3.%20Semantics/reverse%20HTTP.pdf

This sounds interesting from our perspective, I think. Others already have 
non-standardized solutions and workarounds, but the use case really seems 
compelling: Instead of connecting to backends, have backends connect to us. An 
interesting question is how to signal the need for more capacity, for which the 
answer probably is a streams usage in h2/3, but I am not sure if an easy 
solution exists for h1.

MoQ

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/4.%20Evolution/MoQ.pdf

My engineer mind got hooked, even though this topic probably has close to zero 
relevance for what I am doing at the moment. Overall impression: The MoQ folks 
could probably benefit from learning about some common caching topics...

Multiplexing in the year 2024

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/4.%20Evolution/multiplexing.pdf

A smart choice of title to maybe not trigger some defensive reflexes, but it was 
really about H3 over QUIC-ish over TLS over TCP. I can see how that could be 
useful besides maybe reducing the maintenance burden: For clients on 
udp-unfriendly networks and for traffic in environments with excellent, 
predictable network infrastructure, where all the quic (re)prioritization tricks 
are not relevant.

DAY3
----

https://daniel.haxx.se/blog/2024/11/14/workshop-season-six-episode-three/

Do you speak http

https://github.com/HTTPWorkshop/workshop2024/blob/main/talks/5.%20Testing/testing.pdf

Vtest had multiple appearances here and I pushed my neglected vtest-related 
tasks further up my list of bad consciousness.

I had to leave during the following break to not risk to miss the one eurostar 
train I really had to take to make it home in time for a birthday...

Nils



-- 

Nils Goroll (he/him)

** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstra?e 32
22301 Hamburg

tel +49 40 28805731
mob +49 170 2723133
fax +49 40 42949753

xmpp://slink at jabber.int.uplex.de/

http://uplex.de/

From scan-admin at coverity.com  Mon Nov 18 08:12:38 2024
From: scan-admin at coverity.com (scan-admin at coverity.com)
Date: Mon, 18 Nov 2024 08:12:38 +0000 (UTC)
Subject: Coverity Scan: Analysis completed for varnish
Message-ID: <673af6f567900_1870ad2c3e7dfe39a87361@prd-scan-dashboard-0.mail>


    Your request for analysis of varnish has been completed successfully.
    The results are available at https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2BKADyCpvUKOL6EWmZljiu6BUNirv33lqHGQsDVQ-2BP2tg6QNq2-2FpfeAVxnw32Pj2zw-3D-3DXPW3_yQhjbMw4LeDZMA4nqwf-2BPKRH1TcZpi4LlAZWuGRhHR2RwGS5T-2B8m-2BlPIA0uhYm6wChZX9rur5rIPARcrjUPmsY3fu4dAF5X9e48-2BS6DQGCtZuugnyYb0DKe7xSZNegAjRI103ojvWUNVEe1kyDiGUxlq2hK-2BeE-2B6WUbTjyY9CCHU9SEHFEPIx1iesx2viqhTzx4Su8uZQDY9DpuuleWZn-2B38tykImWrbuTseElIQcDY-3D

    Build ID: 654844

    Analysis Summary:
       New defects found: 0
       Defects eliminated: 0


From scan-admin at coverity.com  Mon Nov 25 08:12:45 2024
From: scan-admin at coverity.com (scan-admin at coverity.com)
Date: Mon, 25 Nov 2024 08:12:45 +0000 (UTC)
Subject: Coverity Scan: Analysis completed for varnish
Message-ID: <6744317cdd34c_1f5e222c3e7dfe39a87369b@prd-scan-dashboard-0.mail>


    Your request for analysis of varnish has been completed successfully.
    The results are available at https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2BKADyCpvUKOL6EWmZljiu6BUNirv33lqHGQsDVQ-2BP2tg6QNq2-2FpfeAVxnw32Pj2zw-3D-3DO3OM_yQhjbMw4LeDZMA4nqwf-2BPKRH1TcZpi4LlAZWuGRhHR0cq2UNFxwySDRw05iSPqmFbCmD-2BugCpYziVHRi-2FFuWgJwyKuFtWs21kf0VDIv6ze9h8qfpHyheduvMHzzmkO2MMHxI-2FgwLOY4ZaG3KzmUaZ4LWIVUV9hoX0lyUp4xfhRMsKGBE015xdnIVEVQ-2BIaZ-2FS19OW-2BNzfIf8gJ-2BLfBVgVrMYAhd8qzjWG4gsO3Je9l8-3D

    Build ID: 656310

    Analysis Summary:
       New defects found: 0
       Defects eliminated: 0


From verelight at gmail.com  Thu Nov  7 17:33:19 2024
From: verelight at gmail.com (Maxwell Shim)
Date: Thu, 07 Nov 2024 17:33:19 -0000
Subject: make check c00057.vtc failed of varnish 6.0.13 on ubuntu 24.04
Message-ID: <CABwbB9A2GfXTBBawqxZ5V05R=joGXP=t1DVa3W957w5T0JW5YA@mail.gmail.com>

Dear Varnish Dev,

I need a little help with this.
Please find a log file.

Also I would like to know if you have plans to upload the varnish 6.0.13
package file for Ubuntu 24.04 nobile. I couldn't find it on packagecloud.
so I tried to compile manually, but it failed.

Kind regards,
Maxwell Shim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20241107/8ad27309/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test-suite.log
Type: application/octet-stream
Size: 50760 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20241107/8ad27309/attachment-0001.obj>