W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt

From: Ross Nicoll <jrn@jrn.me.uk>
Date: Fri, 15 Jun 2012 15:50:51 +0100
Message-ID: <4FDB4BCB.9060807@jrn.me.uk>
To: ietf-http-wg@w3.org
I believe the intention is that the client knows where to attribute 
blame; a 403 from a site would mean that the site is rejecting the 
request (and therefore I should talk to the admins if I feel this is in 
error), a 451 (or otherwise) would indicate a third party is rejecting 
the request (and therefore I need to talk to that third party instead).

(I did actually originally argue 403 was sufficient, but feel a good 
case has been made for there needing to be an extra code)

Ross

On 15/06/2012 15:43, Cullen Jennings wrote:
> When trying to decide if a new error code is needed in a protocol, I often ask myself "what should the receiver of this new error code do differently when it gets the new error code". Could you say more about what is the semantic meaning of this error code to the client and how that client should behave when receiving it? I'm particularly interested in how that differs from existing error codes.
>
> Thanks, Cullen
>
>
>
> On Jun 11, 2012, at 7:36 PM, Tim Bray wrote:
>
>> With apologies to MNot for ignoring his opinion (which I generally
>> agree with) about not picking particular
>> status values; but in this case I yielded to temptation.
>>
>> rfc2xml output at
>> http://www.tbray.org/tmp/draft-tbray-http-legally-restricted-status.html
>>
>> -T
>>
>> ---------- Forwarded message ----------
>> From:<internet-drafts@ietf.org>
>> Date: Mon, Jun 11, 2012 at 6:33 PM
>> Subject: New Version Notification for
>> draft-tbray-http-legally-restricted-status-00.txt
>> To: tbray@textuality.com
>>
>> A new version of I-D, draft-tbray-http-legally-restricted-status-00.txt
>> has been successfully submitted by Tim Bray and posted to the
>> IETF repository.
>>
>> Filename:        draft-tbray-http-legally-restricted-status
>> Revision:        00
>> Title:           A New HTTP Status Code for Legally-restricted Resources
>> Creation date:   2012-06-11
>> WG ID:           Individual Submission
>> Number of pages: 5
>> URL:
>> http://www.ietf.org/internet-drafts/draft-tbray-http-legally-restricted-status-00.txt
>> Status:
>> http://datatracker.ietf.org/doc/draft-tbray-http-legally-restricted-status
>> Htmlized:        http://tools.ietf.org/html/submission.filename }}-00
>>
>>
>> Abstract:
>>    This document specifies an additional Hypertext Transfer Protocol
>>    (HTTP) status code for use when resource access is denied for legal
>>    reasons.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>
Received on Friday, 15 June 2012 14:51:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 June 2012 14:51:29 GMT