public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gabriel Goller <g.goller@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-backup] ui: add consent banner maxLength
Date: Tue, 10 Dec 2024 11:27:53 +0100	[thread overview]
Message-ID: <imjmi3ksv7quqjopx4wy6qgdtljsarkvbobpdlsne5bqgjhhh4@uwxhilxilzbv> (raw)
In-Reply-To: <pmqzrrr56aucbodbwoddv2n6mfej3xoqnk3msbt5vuwmmkjrps@nguu7jajt4aw>

On 10.12.2024 11:25, Gabriel Goller wrote:
>On 09.12.2024 12:29, Thomas Lamprecht wrote:
>>Am 06.12.24 um 13:23 schrieb Gabriel Goller:
>>>Add a maxLength of 24000 to the consentBanner. This is the same limit as
>>>in PVE, and while it makes sense there (file size limits in pmxcfs), it
>>>acts more as an arbitrary stop-gap here.
>>>
>>>Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
>>>---
>>> www/config/NodeOptionView.js | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>>diff --git a/www/config/NodeOptionView.js b/www/config/NodeOptionView.js
>>>index c327356f7f24..966e6d719469 100644
>>>--- a/www/config/NodeOptionView.js
>>>+++ b/www/config/NodeOptionView.js
>>>@@ -59,6 +59,9 @@ Ext.define('PBS.NodeOptionView', {
>>> 	    name: 'consent-text',
>>> 	    text: gettext('Consent Text'),
>>> 	    deleteEmpty: true,
>>>+	    fieldOpts: {
>>>+		maxLength: 24000,
>>
>>But that's frontend only? So not really a limitation for anybody.
>>While it is great to have for UX, the real check should go into
>>the backend.
>
>Right, I'll add a limit to the api as well.
>Note that we also have a request body size limit
>(proxmox-rest-server/src/rest.rs:409), which I think is quite sensible,
>so I'd set the frontend limit to the request body limit -1024 (for other
>options to coexist) (so 63 * 1024) and I'll set the backend limit to
>128kB that you suggested.

No I'm stupid that won't help anything.
I'll have to set the backend limit when updating to the 63*1024 as well.
I could set a limit when reading though, but that seems a bit harsh.


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


  reply	other threads:[~2024-12-10 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 12:23 Gabriel Goller
2024-12-09 11:29 ` Thomas Lamprecht
2024-12-10 10:25   ` Gabriel Goller
2024-12-10 10:27     ` Gabriel Goller [this message]
2024-12-10 10:36       ` Gabriel Goller
2024-12-10 15:48 ` Gabriel Goller

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=imjmi3ksv7quqjopx4wy6qgdtljsarkvbobpdlsne5bqgjhhh4@uwxhilxilzbv \
    --to=g.goller@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