Re: #296: 203 Non-Authoritative Information: deprecate?

In message <4DEF6761.1000605@gmx.de>, Julian Reschke writes:
>On 2011-06-08 13:57, Poul-Henning Kamp wrote:

>> 203 should just be dropped.
>> ...
>
>Well, we just came to the conclusion a few days ago that we can't drop it.

Then keep it, and give it a sensible definition, without inventing
a new class of unnecessary HTTP mangling beasts.

Suggestion:

	203 Non-Authoritative Information

	For reasons not specified, the response is not authoritative,
	but expected to be sufficiently indicative of what the
	authoritative response would have been, that it merits
	attention.  Users should be alerted to this fact if the
	client decides to present the response.  One example use
	could be proxies returning expired copies when the origin
	server is unreachable.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Received on Wednesday, 8 June 2011 12:23:41 UTC