> Then you write that content served with a "Content-Encoding: gzip" > header "should" be decompressed by lynx, which, to me, implied that > it wasn't happening in some cases. But that wasn't what the > original poster was talking about.
I'm sorry to confuse you and the delay in my reply. I wanted to report 2 unexpected behaviors in downloading file. 1. Lynx saves the transmission stream data (gzipped data) when the content is served with a "Content-Encoding: gzip" header. 2. Lynx adds the file extention "gzip" in some cases and doesn't add any file extention in other cases in the situation same as 1. So I think Thorsten wrote the same problem as 1. -- Takeshi Hataguchi E-mail: [email protected] From: L A Walsh <[email protected]> Subject: Re: [Lynx-dev] Unexpected behavior downloading Lynx's binary Date: Sun, 01 Jan 2017 17:13:25 -0800 > Thorsten Glaser wrote: >> L A Walsh dixit: >> >>> The "Content-Encoding" gzip is a feature of many web-server software >>> packages. Your client would automatically uncompress it before >>> storing it. This is independent of any file format. >> That’s precisely what I said, thank you for repeating it. > --- > Did you mean in this message?: > > Thorsten Glaser wrote: >> No. >> >> What he means (I think — I occasionally experience a similar problem) >> is that content served with a “Content-Encoding: gzip” header should >> be decompressed by lynx before being saved by the (D)ownload process >> (or passed to a DOWNLOADER utility). > --- > Since I wasn't clear what you were saying. > You said you experience a similar problem, which confused > me, as I didn't see what the problem was. > > Then you write that content served with a "Content-Encoding: gzip" > header "should" be decompressed by lynx, which, to me, implied that > it wasn't happening in some cases. But that wasn't what the > original poster was talking about. It seemed they were confused > about the use of "Content...gzip" in the header and the fact that the files > were bzip2 or "zoo" -- and that they were not > gzipped files. > > I was saying that the two are completely separate - and, unlike > what you wrote, I didn't have or see any problem with such. I > still don't know what problem you experience -- but I didn't see it being the > same as the poster problem which was just being > "confused". If that was your problem, as well, then I understand > why I might be confused about what you meant! :-) > > Or were you expressing a bit of sarcasm in your thanking me for > repeating your point? > > cheers! > -linda > > p.s. I only joined the list shortly before I posted my question > about how to get coloring to work, so if you posted anything > before that, I didn't see it... > > > _______________________________________________ > Lynx-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lynx-dev _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
