all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>,
	"Sebastián Monía" <sebastian@sebasmonia.com>
Cc: ozzloy@challenge-bot.com, 65973@debbugs.gnu.org, ozzloy@gmail.com
Subject: bug#65973: [PATCH] ; send filename, not full path, on EWW form submit
Date: Thu, 7 Nov 2024 10:52:51 -0800	[thread overview]
Message-ID: <05a30678-02e0-20fa-4f0b-9238f9a9081a@gmail.com> (raw)
In-Reply-To: <4215339a-e797-6198-2e40-8d577e1fec42@gmail.com>

On 11/5/2024 11:36 AM, Jim Porter wrote:
> I see three possible reasons: 1) there could be (probably minor) privacy 
> issues with sending the directory structure along to a server; 2) as far 
> as I'm aware, other browsers only pass the "leaf" of the filename; 3) 
> RFC 2813 says that *recipients* should ignore any directories:

Just in case people get confused here (I did, upon re-reading my 
message): The correct RFC is 2183, not 2813.





      parent reply	other threads:[~2024-11-07 18:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  6:10 bug#65973: [PATCH] ; send filename, not full path, on EWW form submit daniel watson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15 11:47 ` Stefan Kangas
2023-09-19  7:15   ` daniel watson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-02 15:02 ` ozzloy
2024-11-05 14:34   ` Sebastián Monía
2024-11-05 17:08     ` Eli Zaretskii
2024-11-05 19:36       ` Jim Porter
2024-11-06  3:30         ` Sebastián Monía
2024-11-06 15:34           ` daniel watson
2024-11-06 23:30         ` Stefan Kangas
2024-11-07  6:20           ` Eli Zaretskii
2024-11-07 18:58             ` Jim Porter
2024-11-08  1:33             ` Stefan Kangas
2024-11-07 18:52         ` Jim Porter [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=05a30678-02e0-20fa-4f0b-9238f9a9081a@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=65973@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=ozzloy@challenge-bot.com \
    --cc=ozzloy@gmail.com \
    --cc=sebastian@sebasmonia.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.