W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1998

Re: FW: Digest mess

From: Joel N. Weber II <devnull@gnu.org>
Date: Mon, 5 Jan 1998 16:41:34 GMT
Message-Id: <199801010134.UAA07226@melange.gnu.org>
To: john@math.nwu.edu
Cc: mogul@pa.dec.com, ietf-http-wg@w3.org, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5121
   Right now I suspect that most
   servers contain routines for decoding base64, but not encoding and most
   clients have routines for encoding and not decoding.

If clients support data: urls, they have to be able to decode base64.
The implentation of base64 is fairly simple; I've seen a 24 line
implmentation of the decoder in the `awk' language.

   If we imagine a day when Basic no longer exists there will be no
   need for base64 in server or client.

I doubt base64 will ever stop existing.  It will probably always be
present for backwards compatibility.  Servers could stop supporting it
(most web servers I use already don't use it, since the info on them is
publicly accessible), but a client might as well keep code that supports
it, in case a user ever needs it.
Received on Wednesday, 7 January 1998 11:41:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:16:29 UTC