On Tue, Mar 04, 2025 at 11:55:02AM +0000, Stuart Henderson wrote: > On 2025-03-04, Rene Kita <m...@rkta.de> wrote: > > On Sat, Mar 01, 2025 at 07:34:31AM -0500, Jon Fineman wrote: > >> I have been having some trouble with emacs/w3m for a while now. > >> > >> When I browse lobste.rs I get the below error message. Using the > >> command line w3m it works fine. duckduckgo.com and a few others also > >> fail. > > > > AFAIK emacs/w3m basically uses 'w3m -dump' to get the rendered page. One > > difference between interactive usage and using -dump is that w3m won't > > ask when there is e.g. a certificate or cookie problem. Instead it will > > fall back to some default. > > This is the compression-related problem again. For some reason it's > now breaking with the reversion of e933cf831f32f but working if > e933cf831f32f is re-applied.
That's strange... I will have a look. Thanks for the pointer! > Repeatable with e.g. > > w3m -dump_source https://duckduckgo.com > w3m -dump_source https://lobste.rs Interestingly I can't reproduce with duckduckgo.com (I even do use it as my search engine), there seems to be some server-side logic about when to do compression.
