From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@sources.redhat.com>
Subject: Re: AW: AW: AW: documentation archive
Date: Thu, 21 Dec 2000 08:43:00 -0000 [thread overview]
Message-ID: <007e01c06b6c$3f19a860$e69460cb@workhorse> (raw)
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E1A1@IIS000>
----- Original Message -----
From: "Bernard Dautrevaux" <Dautrevaux@microprocess.com>
To: "'Earnie Boyd'" <earnie_boyd@yahoo.com>; "Larry Hall (RFK Partners,
Inc)" <lhall@rfk.com>; <cygwin@sources.redhat.com>
Sent: Friday, December 22, 2000 3:05 AM
Subject: RE: AW: AW: AW: documentation archive
> > -----Original Message-----
> > From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
> > Sent: Wednesday, December 20, 2000 5:11 PM
> > To: Larry Hall (RFK Partners, Inc); cygwin@sources.redhat.com
> > Subject: RE: AW: AW: AW: documentation archive
> >
> >
> Are you sure of that ? I was thinking that unrecognized files were always
> transfered as binary data and BTW, I'm not sure that IE5 has any knowledge
> of a '.gz' suffix :-)
>
> Note that as windows FTP client are concerned they effectively try to use
> the suffix to choose between binary and text format while UNIX clients
> ususally ALWAYS use text format unless explicitely directed to binary mode
> :-)
>
> Regards,
>
> Bernard
>
Check out rfc 2616 - Ie 5.5 (possibly 5.0) supports content-encoding,
allowing it to download any file in a compressed format and decompress to
the users chosen filetype on arrival. So .tar.gz becomes .tar. However it is
at least slightly broken - it doesn't rename it (default will save as
.tar.gz still) and it should only decompress when the HTTP server send a
Content-Encoding header AND a different mime type header...
Rob
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2000-12-21 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 6:20 Bernard Dautrevaux
2000-12-21 8:43 ` Robert Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-21 6:14 Bernard Dautrevaux
2000-12-20 8:11 Earnie Boyd
2000-12-20 7:49 Earnie Boyd
2000-12-20 8:02 ` Larry Hall (RFK Partners, Inc)
2000-12-20 5:31 Bernard Dautrevaux
2000-12-20 13:42 ` Jari Aalto+list.cygwin
2000-12-20 3:36 Schaible, Joerg
2000-12-20 4:24 ` Gerrit P. Haase
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='007e01c06b6c$3f19a860$e69460cb@workhorse' \
--to=robert.collins@itdomain.com.au \
--cc=cygwin@sources.redhat.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.
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).