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

Re: Semantics of chunk-exts?

From: Jim Gettys <jg@pa.dec.com>
Date: Wed, 28 Apr 1999 08:09:23 -0700
Message-Id: <9904281509.AA23110@pachyderm.pa.dec.com>
To: John Stracke <francis@ecal.com>
Cc: http-wg@hplb.hpl.hp.com

> Sender: francis@barrayar.appoint.lan
> From: John Stracke <francis@ecal.com>
> Resent-From: http-wg@hplb.hpl.hp.com
> Date: Wed, 28 Apr 1999 13:51:14 +0000
> To: http-wg@hplb.hpl.hp.com
> Subject: Semantics of chunk-exts?
> -----
> I'm implementing Transfer-Encoding: chunked, and I'm trying to
> figure out what to do if I get a chunk-ext I don't understand
> (which is to say, any chunk-ext, since RFC-2068 doesn't define
> any).  Currently I ignore it and log a warning, on the theory
> that any future extension should be backwards compatible--but
> 2068 is silent on whether I can expect compatibility, and I'm not
> sure what kind of compatible extensions might make sense anyway.
> Any advice?

Yes, in general you can expect compatibility.  You must ignore the
extension and continue.

At this date, you should be implementing to the draft standard;
pick up the last internet draft (the RFC editor has not yet issued
the RFC, though the IESG has approved it).
			- Jim
Received on Wednesday, 28 April 1999 16:10:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:23 UTC