Add new http status code - 451 #4327

Closed
wants to merge 1 commit into
from

Projects

None yet

7 participants

@mbarinov

HTTP Status Code for Legally-restricted Resources http://tools.ietf.org/html/draft-tbray-http-legally-restricted-status-00

@bnoordhuis
Member

Thanks but this won't be merged until the draft becomes a standard.

@mbarinov

Unfortunately, it is very necessary in Russia. link Much people support this http status code, link Maybe you'll make an little exception?

@bnoordhuis
Member

Is the status code actually being used today?

@mbarinov

Now thankfully not, but it can change quickly. In Russia, the law adopted on November 1. http://www.bbc.co.uk/news/technology-20096274

@isaacs
isaacs commented Nov 29, 2012

That's very sad for the Russian people. However, like all HTTP status code drafts, we're not going to accept it until the draft is standardized.

@kolobus
kolobus commented Feb 6, 2013

That's intresting, because IETF in discussions about drafts on a first place check if subj. is actually already used/developed/implemented somewhere. Gotta circle here.

@Nodejs-Jenkins

Can one of the admins verify this patch?

@linclark
linclark commented Nov 6, 2014

It looks like the draft has expired, so this issue should likely be closed.

@linclark linclark referenced this pull request in nodebugme/discussion Nov 6, 2014
Open

Add a shortcut to "Suggest this issue be closed" #3

@linclark

Looks like Tim Bray just refreshed this draft, so it might become a standard yet.

@jasnell jasnell added the P-3 label Jun 1, 2015
@jasnell
Member
jasnell commented Jun 24, 2015

Marking this as a "defer" to the converged repo. It's not likely to land here but going to keep it open for now.

@jasnell
Member
jasnell commented Aug 3, 2015

Closing due to lack of activity. Can revisit if someone is interested in updating the PR. Given that this is a feature request, however, it would need to be targeted at either http://github.com/nodejs/io.js or http://github.com/nodejs/node

@jasnell jasnell closed this Aug 3, 2015
@joaocgreis joaocgreis pushed a commit to janeasystems/node-v0.x-archive that referenced this pull request Jan 18, 2016
@claudiorodriguez @jasnell claudiorodriguez + jasnell doc: add path property to Write/ReadStream in fs.markdown
Documents the "path" property on fs.WriteStream
and fs.ReadStream. See #4327

PR-URL: nodejs/node#4368
Reviewed-By: James M Snell <jasnell@gmail.com>
310530b
@richardlau richardlau pushed a commit to ibmruntimes/node that referenced this pull request Jan 21, 2016
@claudiorodriguez @evanlucas claudiorodriguez + evanlucas doc: add path property to Write/ReadStream in fs.markdown
Documents the "path" property on fs.WriteStream
and fs.ReadStream. See #4327

PR-URL: nodejs/node#4368
Reviewed-By: James M Snell <jasnell@gmail.com>
a6c242f
@richardlau richardlau pushed a commit to ibmruntimes/node that referenced this pull request Feb 15, 2016
@claudiorodriguez @MylesBorins claudiorodriguez + MylesBorins doc: add path property to Write/ReadStream in fs.markdown
Documents the "path" property on fs.WriteStream
and fs.ReadStream. See #4327

PR-URL: nodejs/node#4368
Reviewed-By: James M Snell <jasnell@gmail.com>
707858b
@richardlau richardlau pushed a commit to ibmruntimes/node that referenced this pull request Feb 17, 2016
@claudiorodriguez @MylesBorins claudiorodriguez + MylesBorins doc: add path property to Write/ReadStream in fs.markdown
Documents the "path" property on fs.WriteStream
and fs.ReadStream. See #4327

PR-URL: nodejs/node#4368
Reviewed-By: James M Snell <jasnell@gmail.com>
75b0ea8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment