[emacs-w3m:13888] Re: [emacs-w3m/emacs-w3m] Problem with brotli compression (Issue #112)
Boruch Baum <[email protected]> Tue, 08 Nov 2022 14:58:57 -0800
| Newsgroups | gmane.emacs.w3m |
|---|---|
| Message-ID | <emacs-w3m/emacs-w3m/issues/112/[email protected]> |
----==_mimepart_636adf319245f_2531c67024883c
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I also have never had the problem, and I frequently use emacs-w3m for=0D
the sites that OP mentions.=0D
=0D
The relevant upstream PR was merged on Feb 11, 2021:=0D
=0D
https://github.com/tats/w3m/pull/164=0D
=0D
My guess is that the reason neither of us has been affected is that=0D
brotli compression needs to be mentioned in the HTTP GET request that=0D
w3m sends, in place of mentioning, for example, gzip, so the mystery of=0D=
which versions of w3m have the issue would just be a configuration=0D
option in w3m.=0D
=0D
My w3m config file (~/.w3m/config) includes the configuration option=0D
"accept_encoding" which for me is "gzip, compress, bzip, bzip2,=0D
deflate". My guess is that OP has "brotli" in that list and prior to=0D
gzip there.=0D
=0D
=0D
On 2022-11-07 15:48, yamaoka wrote:=0D
> Thank you very much for the information. I've added the brotli entry=
to=0D
> w3m-decoder-alist and w3m-encoding-alist.=0D
>=0D
> Though I've never faced with such a page seen like binary, I've=0D
> installed the brotli executable in my box. ;-)=0D
>=0D
> =E2=80=94=0D
> Reply to this email directly, [1]view it on GitHub, or [2]unsubscrib=
e.=0D
> You are receiving this because you are subscribed to this thread.=0D=
> Message ID: ***@***.***>=0D
>=0D
> References=0D
>=0D
> 1. https://github.com/emacs-w3m/emacs-w3m/issues/112#issuecomment-13=
06383393=0D
> 2. https://github.com/notifications/unsubscribe-auth/AAOE3KHKCX47JOW=
7GP7LDKTWHGIMXANCNFSM6AAAAAARZR2FZU=0D
=0D
-- =0D
hkp://keys.gnupg.net=0D
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0=0D
=0D
=0D
-- =0D
Reply to this email directly or view it on GitHub:=0D
https://github.com/emacs-w3m/emacs-w3m/issues/112#issuecomment-1307949558=
=0D
You are receiving this because you are subscribed to this thread.=0D
=0D
Message ID: <emacs-w3m/emacs-w3m/issues/112/[email protected]>=
----==_mimepart_636adf319245f_2531c67024883c
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p></p>=0D
I also have never had the problem, and I frequently use emacs-w3m for<br>=
=0D
the sites that OP mentions.<br>=0D
<br>=0D
The relevant upstream PR was merged on Feb 11, 2021:<br>=0D
<br>=0D
https://github.com/tats/w3m/pull/164<br>=0D
<br>=0D
My guess is that the reason neither of us has been affected is that<br>=0D=
brotli compression needs to be mentioned in the HTTP GET request that<br>=
=0D
w3m sends, in place of mentioning, for example, gzip, so the mystery of<b=
r>=0D
which versions of w3m have the issue would just be a configuration<br>=0D=
option in w3m.<br>=0D
<br>=0D
My w3m config file (~/.w3m/config) includes the configuration option<br>=0D=
"accept_encoding" which for me is "gzip, compress, bzip, b=
zip2,<br>=0D
deflate". My guess is that OP has "brotli" in that list an=
d prior to<br>=0D
gzip there.<br>=0D
<br>=0D
<br>=0D
On 2022-11-07 15:48, yamaoka wrote:<br>=0D
> Thank you very much for the information. I've added the brotl=
i entry to<br>=0D
> w3m-decoder-alist and w3m-encoding-alist.<br>=0D
><br>=0D
> Though I've never faced with such a page seen like binary, I&=
#39;ve<br>=0D
> installed the brotli executable in my box. ;-)<br>=0D
><br>=0D
> =E2=80=94<br>=0D
> Reply to this email directly, [1]view it on GitHub, or [2]unsubsc=
ribe.<br>=0D
> You are receiving this because you are subscribed to this thread.=
<br>=0D
> Message ID: ***@***.***><br>=0D
><br>=0D
> References<br>=0D
><br>=0D
> 1. https://github.com/emacs-w3m/emacs-w3m/issues/112#issuecomment=
-1306383393<br>=0D
> 2. https://github.com/notifications/unsubscribe-auth/AAOE3KHKCX47=
JOW7GP7LDKTWHGIMXANCNFSM6AAAAAARZR2FZU<br>=0D
<br>=0D
-- <br>=0D
hkp://keys.gnupg.net<br>=0D
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0<br>=0D
=0D
=0D
<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />Reply to this email directly, <a href=3D"https://github.com/em=
acs-w3m/emacs-w3m/issues/112#issuecomment-1307949558">view it on GitHub</=
a>, or <a href=3D"https://github.com/notifications/unsubscribe-auth/ALIUP=
NY7ERID4EYOW7KO2XTWHLLLDANCNFSM6AAAAAARZR2FZU">unsubscribe</a>.<br />You =
are receiving this because you are subscribed to this thread.<img src=3D"=
https://github.com/notifications/beacon/ALIUPN4DHAIO7KGW5TQC7GLWHLLLDA5CN=
FSM6AAAAAARZR2FZWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5=
UWJTSN6W47M.gif" height=3D"1" width=3D"1" alt=3D"" /><span style=3D"color=
: transparent; font-size: 0; display: none; visibility: hidden; overflow:=
hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; ms=
o-hide: all">Message ID: <span><emacs-w3m/emacs-w3m/issues/112/1307949=
558</span><span>@</span><span>github</span><span>.</span><span>com></s=
pan></span></p>=0D
<script type=3D"application/ld+json">[=0D
{=0D
"@context": "http://schema.org",=0D
"@type": "EmailMessage",=0D
"potentialAction": {=0D
"@type": "ViewAction",=0D
"target": "https://github.com/emacs-w3m/emacs-w3m/issues/112#issuecomment=
-1307949558",=0D
"url": "https://github.com/emacs-w3m/emacs-w3m/issues/112#issuecomment-13=
07949558",=0D
"name": "View Issue"=0D
},=0D
"description": "View this Issue on GitHub",=0D
"publisher": {=0D
"@type": "Organization",=0D
"name": "GitHub",=0D
"url": "https://github.com"=0D
}=0D
}=0D
]</script>=
----==_mimepart_636adf319245f_2531c67024883c--