public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Max Carrara <m.carrara@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] fix #5217: api: send missing header when upgrading to HTTP/2
Date: Thu, 29 Feb 2024 16:26:51 +0100	[thread overview]
Message-ID: <fc00fc93-fe70-4b96-80a1-adf167c1039a@proxmox.com> (raw)
In-Reply-To: <e9af7136-e5ff-4190-8d5f-eebe6030da73@proxmox.com>

On 2/28/24 19:03, Thomas Lamprecht wrote:
> Am 28/02/2024 um 17:20 schrieb Max Carrara:
>> Caddy therefore does not deviate from the HTTP/1.1 and HTTP/2
>> specifications; neither to we. I therefore conclude that it's best to
>> just include the header in this specific response anyway, as no harm
>> is done by doing so.
>>
> 
> can be fine, but is there any discussion about this from Caddy's site?

I haven't found anything, no.

> 
> As while we can take this in and PBS should work with Caddy in-between,
> other HTTP/2 daemons that follow spec while not having that header
> still won't work.
> So, if there isn't any issue tracker entry for this at caddy's side it
> might be worth opening one even if we apply this here, and if there's
> an existing issue then referencing it here would be great.

I've opened a more detailed issue over on Caddy's GitHub where I've
described pretty much everything I had discovered [0]. Most of the
information there regarding the RFC specs and whatnot are already in the
commit message of the patch.

I'd say we wait a little bit and see what the Caddy folks' opinions are on
this before we apply this patch in case some additional things / infos turn
up that might be of relevance.

In either case I'll send in a v2 with an updated commit message once there's
been some progress in that regard. Will reference the issue in the message
as well (and might reword some things, now that I've read it again).

[0]: https://github.com/caddyserver/caddy/issues/6134




      reply	other threads:[~2024-02-29 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 16:20 Max Carrara
2024-02-28 18:03 ` Thomas Lamprecht
2024-02-29 15:26   ` Max Carrara [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fc00fc93-fe70-4b96-80a1-adf167c1039a@proxmox.com \
    --to=m.carrara@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal