From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox 1/1] auth-api: include meta information required by extjs in api endpoints
Date: Wed, 23 Jul 2025 17:18:27 +0200 [thread overview]
Message-ID: <DBJJ9VV9LYJJ.5NJ3TJ14M2WU@proxmox.com> (raw)
In-Reply-To: <59a4e51b-5459-462b-b26c-6c70649a0ad3@proxmox.com>
On Tue Jul 22, 2025 at 10:21 PM CEST, Thomas Lamprecht wrote:
> Am 16.07.25 um 10:17 schrieb Shannon Sterz:
>> On Wed Jul 16, 2025 at 12:40 AM CEST, Thomas Lamprecht wrote:
>>> Am 10.07.25 um 15:50 schrieb Shannon Sterz:
>>>> otherwise extjs will assume the requests failed even though they were
>>>> successful.
>>>
>>> Potentially dumb question, but is this then only returning that for the
>>> extjs formatter or also for the json one?
>>
>> sadly this impacts all formaters as this type of api handler returns a
>> `Response` right away instead of a passing it through a formater like
>> other handler types. the problem with the other handler types is, that
>> they don't let you access the requests header values as easily.
>>
>> the nicest way to resolve this would probably be to pass down the
>> formater in `handle_api_request` [1] to endpoints that return an
>> `ApiResponseFuture`. so that they can handle the formatting themselves
>> (some api endpoints like those that download raw text files etc.
>> probably won't need the formater).
>
> It might be better to expose through the (RPC/REST) environment in the
> mid term, could be useful for other stuff too. Or alternatively expose
> a structured way to pass back a cookie if the methods signals support
> in the schema.
>
> But either way: we can go this route for now, while looking at this more
> closely down the line, when it either causes problems (IMO unlikely) or
> when we need something similar for another reason anyway and can clean
> this up here then too.
>
> Anyway, if you get someone to give this a spin and at least a T-b here,
> ideally a review too, I'd be still open to take this in.
alright, mira and maximiliano both tested the series and found mostly
cosmetic issues. i adopted them into a v2 and kept their T-b lines since
nothing really changed except for an additional `tracing::debug!`
statement. let me know if there is something else i can do.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-07-23 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 13:50 [pbs-devel] [PATCH proxmox{, -backup} 0/4] http only cookie based tickets for pbs Shannon Sterz
2025-07-10 13:50 ` [pbs-devel] [PATCH proxmox 1/1] auth-api: include meta information required by extjs in api endpoints Shannon Sterz
2025-07-15 22:40 ` Thomas Lamprecht
[not found] ` <DBDBXGTI71WP.3V2J3DEMNK1DL@proxmox.com>
2025-07-22 20:21 ` Thomas Lamprecht
2025-07-23 15:18 ` Shannon Sterz [this message]
2025-07-10 13:50 ` [pbs-devel] [PATCH proxmox-backup 1/3] api: access: add opt-in http only ticket authentication flow Shannon Sterz
2025-07-23 12:57 ` Mira Limbeck
2025-07-23 13:58 ` Maximiliano Sandoval
2025-07-10 13:50 ` [pbs-devel] [PATCH proxmox-backup 2/3] ui: opt into the new http-only " Shannon Sterz
2025-07-10 13:50 ` [pbs-devel] [PATCH proxmox-backup 3/3] client: adapt pbs client to also handle http-only flows correctly Shannon Sterz
2025-07-23 12:56 ` [pbs-devel] [PATCH proxmox{, -backup} 0/4] http only cookie based tickets for pbs Mira Limbeck
2025-07-23 14:05 ` Maximiliano Sandoval
2025-07-23 15:15 ` Shannon Sterz
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=DBJJ9VV9LYJJ.5NJ3TJ14M2WU@proxmox.com \
--to=s.sterz@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