From: Yuri Khan <yuri.v.khan@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs-w3m question
Date: Mon, 7 Nov 2022 13:59:26 +0700 [thread overview]
Message-ID: <CAP_d_8VGmSnqiau-kHTvqUxfxZXt8UbaMnwthjH6yC8WgWNrXw@mail.gmail.com> (raw)
In-Reply-To: <jwv4jvbxo2e.fsf-monnier+emacs@gnu.org>
On Mon, 7 Nov 2022 at 13:47, Stefan Monnier via Users list for the GNU
Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Yuri Khan [2022-11-07 13:08:44] wrote:
> > After re-reading RFC 9110 § 12.5.3, it looks like the client should
> > indicate its supported and preferred content encodings in an
> > Accept-Encoding request header. Does w3m.el send one? If it doesn’t,
> > the server may assume any encoding is acceptable.
>
> Really? That doesn't sound right. Shouldn't the server assume that
> only the simplest encodings can be used if the header is missing?
> That's the only safe choice, no?
Yeah, my intuition also said so and I was about to compose a reply of
indignant finger pointing at the sites that spew brotli without any
indication that the client would be able to process it, but I decided
to look up the spec and changed my mind.
This is what it says, after explaining the syntax:
: A server tests
: whether a content coding for a given representation is acceptable
: using these rules:
:
: 1. If no Accept-Encoding header field is in the request,
: any content coding is considered acceptable by the user agent.
: 2. If the representation has no content coding,
: then it is acceptable by default
: unless specifically excluded by the Accept-Encoding header field
: stating either "identity;q=0" or "*;q=0"
: without a more specific entry for "identity".
: 3. If the representation's content coding is one of the content codings
: listed in the Accept-Encoding field value,
: then it is acceptable unless it is accompanied by a qvalue of 0.
: (As defined in Section 12.4.2,
: a qvalue of 0 means "not acceptable".)
I checked and similar wordings run back through the original HTTP/1.1
spec (RFC 2616). That version also includes the following:
: Note: If the request does not include an Accept-Encoding field,
: and if the "identity" content-coding is unavailable, then
: content-codings commonly understood by HTTP/1.0 clients (i.e.,
: "gzip" and "compress") are preferred; some older clients
: improperly display messages sent with other content-codings. The
: server might also make this decision based on information about
: the particular user-agent or client.
next prev parent reply other threads:[~2022-11-07 6:59 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 20:25 emacs-w3m question Jon Fineman
2022-11-02 12:32 ` Michael Heerdegen
2022-11-02 17:44 ` Jon Fineman
2022-11-03 11:18 ` Michael Heerdegen
2022-11-08 3:58 ` Bob Newell
2022-11-02 13:20 ` Emanuel Berg
2022-11-02 17:32 ` Jon Fineman
2022-11-02 18:22 ` Emanuel Berg
2022-11-03 17:56 ` Bob Newell
2022-11-04 2:02 ` Jon Fineman
2022-11-06 22:49 ` Bob Newell
2022-11-07 6:08 ` Yuri Khan
2022-11-07 6:38 ` Bob Newell
2022-11-07 6:45 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-07 6:59 ` Yuri Khan [this message]
2022-11-07 12:34 ` Emanuel Berg
2022-11-07 12:40 ` Emanuel Berg
2022-11-02 22:14 ` Bob Newell
-- strict thread matches above, loose matches on Subject: below --
2008-10-27 20:45 Francis Moreau
2008-10-27 21:09 ` henry atting
2008-10-27 21:36 ` Richard Riley
2008-10-28 18:40 ` Xah
2008-10-30 21:25 ` Xavier Maillard
2008-10-30 22:16 ` Paul R
2008-11-01 7:25 ` Xavier Maillard
2008-11-01 12:59 ` Paul R
[not found] ` <mailman.2625.1225539334.25473.help-gnu-emacs@gnu.org>
2008-11-01 15:51 ` Richard Riley
2008-11-03 11:25 ` Xavier Maillard
2008-11-03 12:13 ` Richard Riley
2008-11-03 23:25 ` Xavier Maillard
[not found] ` <mailman.2907.1225862955.25473.help-gnu-emacs@gnu.org>
2008-11-05 13:23 ` Xah
[not found] ` <mailman.2522.1225402310.25473.help-gnu-emacs@gnu.org>
2008-10-30 22:38 ` Xah
2008-11-03 11:25 ` Xavier Maillard
2008-11-03 12:36 ` Paul R
2008-11-03 23:25 ` Xavier Maillard
[not found] ` <mailman.2772.1225715774.25473.help-gnu-emacs@gnu.org>
2008-11-03 13:27 ` Richard Riley
2008-11-04 13:19 ` Chris McMahan
2008-11-04 14:19 ` Richard Riley
2008-11-05 7:25 ` Xavier Maillard
[not found] ` <mailman.2764.1225711684.25473.help-gnu-emacs@gnu.org>
[not found] ` <4d476218-bd76-4d41-8a12-1428dfba9e9b@s9g2000prg.googlegroups.com>
2008-11-05 7:25 ` Xavier Maillard
[not found] ` <mailman.2966.1225952942.25473.help-gnu-emacs@gnu.org>
2008-11-06 14:31 ` Xah
2008-11-06 16:32 ` Alan Mackenzie
2008-11-06 18:12 ` Giorgos Keramidas
2008-11-07 1:22 ` Xah
2008-11-07 3:50 ` Giorgos Keramidas
2008-11-07 5:42 ` Xah
2008-11-07 7:48 ` Giorgos Keramidas
2008-11-07 8:07 ` Xah
[not found] ` <mailman.3000.1225988502.25473.help-gnu-emacs@gnu.org>
2008-11-07 1:01 ` Xah
2008-11-07 10:04 ` Alan Mackenzie
2008-11-07 10:29 ` Paul R
2008-11-07 23:51 ` Alan Mackenzie
2008-11-08 1:14 ` Lennart Borgman
2008-11-10 21:25 ` Xavier Maillard
2008-11-10 21:25 ` Xavier Maillard
[not found] ` <mailman.3052.1226051600.25473.help-gnu-emacs@gnu.org>
2008-11-07 17:43 ` Xah
2008-11-06 18:02 ` Alan Mackenzie
2008-11-07 6:24 ` Kevin Rodgers
[not found] ` <mailman.3010.1225993912.25473.help-gnu-emacs@gnu.org>
2008-11-06 20:02 ` Rupert Swarbrick
2008-11-07 2:02 ` Xah
2008-11-07 10:24 ` Eli Zaretskii
2008-11-07 10:54 ` Alan Mackenzie
[not found] ` <mailman.3055.1226054611.25473.help-gnu-emacs@gnu.org>
2008-11-07 20:10 ` Xah
2008-11-08 18:57 ` Rupert Swarbrick
2008-11-08 21:33 ` Xah
2008-11-09 6:26 ` Wei Weng
2008-11-09 8:55 ` Xah
2008-11-10 21:25 ` Xavier Maillard
[not found] ` <mailman.21.1226352538.26697.help-gnu-emacs@gnu.org>
2008-11-10 22:38 ` Xah
2008-11-12 2:28 ` Sean Sieger
2008-11-01 13:03 ` Andreas Politz
2008-11-03 11:25 ` Xavier Maillard
[not found] ` <mailman.2763.1225711681.25473.help-gnu-emacs@gnu.org>
2008-11-06 16:51 ` Andreas Politz
2008-10-27 21:48 ` Andreas Politz
2008-10-28 10:50 ` Francis Moreau
2008-10-28 14:51 ` OtherMichael
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=CAP_d_8VGmSnqiau-kHTvqUxfxZXt8UbaMnwthjH6yC8WgWNrXw@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).