That is a dumb error code. 404 already exists.
404 is for "not found". 451 would be for "found, but we can't show it to you".
"The server understood the request, but is refusing to fulfill it" is already 403.
91–93 of 93 posts
Earlier quoted context omitted.
Yes, but that's true of other standards. Eg, I can start putting tags in my HTML if I want. The issue is whether anyone else will expect this tag or code and do anything meaningful with it.
I get what you mean but I don't think this is the same thing. HTML has a DTD, something that people conform to when writing, so your tag would not follow that guideline, whereas companies like Twitter can implement their own error codes as they see fit. See error code 420, Enhance Your Calm.[0] [0]: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Earlier quoted context omitted.
From http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html "10.4 Client Error 4xx The 4xx class of status code is intended for cases in which the client seems to have erred. " The client has not erred by requested a document that exists and which the server can technically provide (separately, the server has not erred by refusing to provide a document to the client which the exists and which access control would all…
> The client has not erred by requested a document that exists and which the server can technically provide The client has erred in requesting a document which the server is legally forbidden to provide to that client. As specified for 403, the server understands the request and refuses to fulfill it. Admittedly, a hypothetical 6xx Third-Party Interference series of error codes might be useful for these kind of cases…
> The client has not erred... the server understands the request and refuses to fulfill it.
As I see it, the server is not refusing anything. +1 6xx Third-Party Interference.
Let's just agree to disagree.