From: Jim Porter <jporterbugs@gmail.com>
To: "Sebastián Monía" <sebastian@sebasmonia.com>,
"Eli Zaretskii" <eliz@gnu.org>
Cc: 73133@debbugs.gnu.org, ganimard@tuta.io
Subject: bug#73133: 29.2; EWW fails to render some webpages
Date: Sun, 20 Oct 2024 12:17:34 -0700 [thread overview]
Message-ID: <eb67dd3a-d78e-71a3-acaf-a50d233dba74@gmail.com> (raw)
In-Reply-To: <87zfn0f03l.fsf@sebasmonia.com>
On 10/19/2024 10:56 AM, Sebastián Monía wrote:
> Thank you everyone for your help in this process.
One last thought before I merge this: I notice that when we can't guess
a Content-Type, we use "text/plain" as a fallback. Per RFC-9110[1], the
fallback should be "application/octet-stream".
I tested this out in EWW, and we still display
"application/octet-stream" pages as text in EWW, so there's no
difference in behavior by default vs "text/plain". However, users who
customize 'eww-use-external-browser-for-content-type' could make pages
like that open externally, which I think makes sense. For non-HTML pages
with no actual Content-Type header, they're at least reasonably likely
to be binary files, so you'd probably want to download them rather than
display them.
Does anyone else have any thoughts on the relative merits of falling
back to "application/octet-stream" vs "text/plain"? If we go with the
former, I can update the patch when I merge.
[1] https://www.rfc-editor.org/rfc/rfc9110#section-8.3-5
next prev parent reply other threads:[~2024-10-20 19:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 20:52 bug#73133: 29.2; EWW fails to render some webpages Ganimard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 6:06 ` Jim Porter
2024-09-21 9:13 ` Eli Zaretskii
2024-09-21 17:12 ` Jim Porter
2024-09-23 15:43 ` Sebastián Monía
2024-09-28 10:58 ` Eli Zaretskii
2024-09-30 15:52 ` Sebastián Monía
2024-09-23 15:56 ` Sebastián Monía
2024-09-24 18:31 ` Jim Porter
2024-09-25 20:46 ` Sebastián Monía
2024-09-26 1:59 ` Jim Porter
2024-09-30 17:10 ` Sebastián Monía
2024-10-03 23:39 ` Jim Porter
2024-10-09 3:30 ` Sebastián Monía
2024-10-09 3:42 ` Jim Porter
2024-10-10 2:08 ` Sebastián Monía
2024-10-14 4:35 ` Jim Porter
2024-10-14 14:03 ` Eli Zaretskii
2024-10-15 11:43 ` Sebastián Monía
2024-10-19 7:46 ` Eli Zaretskii
2024-10-19 17:56 ` Sebastián Monía
2024-10-20 19:17 ` Jim Porter [this message]
2024-10-21 1:48 ` Sebastián Monía
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eb67dd3a-d78e-71a3-acaf-a50d233dba74@gmail.com \
--to=jporterbugs@gmail.com \
--cc=73133@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ganimard@tuta.io \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).