Since it's a server error, it should be in the 500 region. Nerd fail!

It's a form of permission denied, not a server error, so it sits more logically with the others in the 400s:

401 Unauthorized
402 Payment Required
403 Forbidden

Really it's just a special case of 403.
>> ^gwiz665:

Since it's a server error, it should be in the 500 region. Nerd fail!

The site is blocked at the ISP level so the request never makes it to the destination, making the 5xx error invalid. Yet the 403 error being server in this instance is also misleading as it is describes te request as valid but the server will not respond to it. To me the "server" means the destination (host server) and not the ISP server.

However unlikely, I do hope that there is a unique identifier created to flag such events.

>> ^oritteropo:

It's a form of permission denied, not a server error, so it sits more logically with the others in the 400s:
401 Unauthorized
402 Payment Required
403 Forbidden
Really it's just a special case of 403.
>> ^gwiz665:
Since it's a server error, it should be in the 500 region. Nerd fail!

Errors 502, 503 and 504 are very often from a server OTHER than the one you want to connect to, so you've actually made a reasonable case for @gwiz665's original assertion... but I agree that it would be far better to have a unique code like 451 to indicate that this has happened.

When I said that the proposed 451 counts as a special case of 403, I didn't mean that it should return 403 just that I saw it as a related concept.
>> ^critical_d:

The site is blocked at the ISP level so the request never makes it to the destination, making the 5xx error invalid. Yet the 403 error being server in this instance is also misleading as it is describes te request as valid but the server will not respond to it. To me the "server" means the destination (host server) and not the ISP server.
However unlikely, I do hope that there is a unique identifier created to flag such events.

Interesting discussion. You all get upvotes.

Server - client in a http context is pretty divided between "me" (client) and the rest (server), which is why things like Bad Gateway (502) is also in the 500 region. 500 is when the error happens "over there", while 400 is when the error is mine. Like with 404, the client provided a bad path, so the server successfully returns a "does not exist" message. The error is thus in the 400 region.


In that sense, you could argue that censorship is 400 because you're accessing something you're not supposed to.