From: daniel watson <ozzloy@each.do>
To: "Sebastián Monía" <sebastian@sebasmonia.com>
Cc: Jim Porter <jporterbugs@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
65973@debbugs.gnu.org, ozzloy@gmail.com
Subject: bug#65973: [PATCH] ; send filename, not full path, on EWW form submit
Date: Wed, 06 Nov 2024 07:34:48 -0800 [thread overview]
Message-ID: <87zfmciczm.fsf@trent-reznor> (raw)
In-Reply-To: <87y11x11l2.fsf@sebasmonia.com>
the rationale was initially #1.
every other browser i looked into sent the filename only. based on
that, i was more confident that it was worth submitting a patch.
#3 seems like a good reason too, but i did not know about that until
reading this thread.
Sebastián Monía <sebastian@sebasmonia.com> writes:
> Jim Porter <jporterbugs@gmail.com> writes:
>> On 11/5/2024 9:08 AM, Eli Zaretskii wrote:
>>> I'd like some rationale for this change. The original report never
>>> explains why sending the full absolute file name to the server is bad.
>>
>> 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: [...]
>> RFC 2813 is primarily about mail clients, but MDN suggests following
>> it in a web context as well:
>> <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition>.
>
>> So I think the RFC would suggest that it's *allowed* to send the
>> directories in the "filename" field, but since the server is supposed
>> to ignore it, there's no benefit to doing so.
>
> I didn't get as far as Jim did. I assumed the concern was #1, and I knew
> the rest of the path is ignored, so figured we should go ahead.
>
> Regards,
> Seb
next prev parent reply other threads:[~2024-11-06 15:34 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 [this message]
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
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=87zfmciczm.fsf@trent-reznor \
--to=ozzloy@each.do \
--cc=65973@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.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.