W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1996

Re: Opinion on Notify Request Header

From: Larry Masinter <masinter@parc.xerox.com>
Date: Mon, 4 Nov 1996 00:42:55 PST
To: yarong@microsoft.com
CC: ejw@ics.uci.edu, w3c-dist-auth@w3.org
Message-Id: <96Nov4.004255pst."2694"@golden.parc.xerox.com>
Oh, so it's a versioning issue, not a client capability issue. That
makes sense. Status might be signalled by a

    102 Processing

status code, probably with an entity body which contains the actual
status. This would signal the client that the server is still working
on the request and not to time out.

We could add a new request header which indicates a client's
willingness to accept such a status code, or else just bundle it in
with HTTP/1.2
	  GET uri HTTP/1.2

would be the signal that '102 processing' responses are acceptable.


Received on Monday, 4 November 1996 03:43:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC