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

ISSUE CREATE: Proposed resolution

From: Henrik Frystyk Nielsen <frystyk@w3.org>
Date: Tue, 28 Jul 1998 14:39:29 -0400
Message-Id: <>
To: jg@w3.org, http-wg@cuckoo.hpl.hp.com
Cc: dmk@research.bell-labs.com, paulle@microsoft.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/262

After further discussions with Jim, we propose the following resolution:

Clarify the existing possibility of including an etag in a 201 response and
don't do anything about potential other metainformation as this is a
problem in many other places as well. Basically, in HTTP it's hard to know
what is metainformation and what is transaction information.

Action: Add this clarification to section 10.2.2:

	A 201 response MAY contain an Etag response header field
	indicating the current value of the entity tag for the
	created requested variant, see [14.19].

Any objections or comments?

Henrik Frystyk Nielsen,
World Wide Web Consortium
Received on Tuesday, 28 July 1998 11:40:36 UTC

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