I've requested help from upstream on curl-library:
https://curl.se/mail/lib-2024-05/0020.html
It looks like the regression is partially back on the 8.7.1 as well:
> HTTP/2 200
> expires: Fri, 01 Jan 1980 00:00:00 GMT
> pragma: no-cache
> cache-control: no-cache, max-age=0, must-revalidate
>
Since 2023-10-02, we have a fixed version of the curl package on
stable-backports, so this can serve as a workaround if you're fine
with the constraints of the backports repository[0].
The current investigation status is that we know which commit caused
the regression and which one fixed it, but
On Sun, Jun 11, 2023 at 01:56:21AM -0400, Sergio Durigan Junior wrote:
> On Saturday, June 10 2023, Samuel Henrique wrote:
>
> > Hello,
> >
> > I'm not able to reproduce the issue on Bookworm with a HTTP2 localhost
> > apache server.
> [...]
>
> Hey,
>
> I was able to find another URL that
On Saturday, June 10 2023, Samuel Henrique wrote:
> Hello,
>
> I'm not able to reproduce the issue on Bookworm with a HTTP2 localhost
> apache server.
[...]
Hey,
I was able to find another URL that triggers the same issue. This one:
Hello,
I'm not able to reproduce the issue on Bookworm with a HTTP2 localhost
apache server.
There's something specific to the way
"https://git.dgit.debian.org/dgit/info/refs; is setup which triggers
the issue.
The next step is to find a server which can be tested against, ideally
finding the
For the record: this bug caused `dgit clone dgit` to fail. That
aspect of the problem has been worked around by forcing that host to
use HTTP/1 only. ([rt.debian.org #9218]).
This also means that the repro in this bug report won't work any more,
I'm afraid.
--
Ian JacksonThese opinions
On Friday, June 09 2023, Ian Jackson wrote:
> Steps to reproduce:
>
> curl -I https://git.dgit.debian.org/dgit/info/refs
>
> Expected output (obtained on, eg, buster):
>
> HTTP/2 200
> expires: Fri, 01 Jan 1980 00:00:00 GMT
> pragma: no-cache
> cache-control: no-cache, max-age=0,
7 matches
Mail list logo
