Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

http status code, 451 #4376

Closed
mbarinov opened this issue Dec 21, 2015 · 1 comment
Closed

http status code, 451 #4376

mbarinov opened this issue Dec 21, 2015 · 1 comment
Labels
feature request Issues that request new features to be added to Node.js. http Issues or PRs related to the http subsystem.

Comments

@mbarinov
Copy link
Contributor

A new http status code, "Unavailable For Legal Reasons".
This http code allows us to provide a fair reason when we can't return some data to the client by legal issues. Also, IETF made it standard. https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/
mbarinov added a commit to mbarinov/node that referenced this issue Dec 21, 2015
@mbarinov
http: 451 status code "Unavailable For Legal Reasons"
a9e260a 
This http code allows us to provide a fair reason when we can't return some data to the client by legal issues.

IETF https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/

Fixes: nodejs#4376
@mbarinov mbarinov mentioned this issue Dec 21, 2015
Closed
@Fishrock123 Fishrock123 added the http Issues or PRs related to the http subsystem. label Dec 21, 2015
@ChALkeR ChALkeR added the feature request Issues that request new features to be added to Node.js. label Dec 21, 2015
mbarinov added a commit to mbarinov/node that referenced this issue Dec 21, 2015
@mbarinov
http: tests for 451 status code
64aa56b 
IETF https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/

Fixes: nodejs#4376
@ChALkeR
Copy link
Member

ChALkeR commented Dec 22, 2015

One more ref: https://twitter.com/mnot/status/677712170038124544

Fishrock123 pushed a commit to Fishrock123/node that referenced this issue Jan 6, 2016
@mbarinov @Fishrock123
http: 451 status code "Unavailable For Legal Reasons"
c77fd68 
This http code allows us to provide a fair reason when
we can't return some data to the client by legal issues.

IETF https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/

Fixes: nodejs#4376
PR-URL: nodejs#4377
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
scovetta pushed a commit to scovetta/node that referenced this issue Apr 2, 2016
@mbarinov
http: 451 status code "Unavailable For Legal Reasons"
07d3a3f 
This http code allows us to provide a fair reason when
we can't return some data to the client by legal issues.

IETF https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/

Fixes: nodejs#4376
PR-URL: nodejs#4377
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this issue Nov 14, 2016
@mbarinov
http: 451 status code "Unavailable For Legal Reasons"
c94482b 
This http code allows us to provide a fair reason when
we can't return some data to the client by legal issues.

IETF https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/

Fixes: #4376
PR-URL: #4377
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Issues that request new features to be added to Node.js. http Issues or PRs related to the http subsystem.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ChALkeR @mbarinov @Fishrock123