Technically speaking 403 can be returned if it's blocked for legal reasons, but obviously it would be nice to know why it is forbidden.
There is some reasoning about this on: http://www.451unavailable.org/why-do-we-need-error-451 Still, imho, 4XX could be a response for a given URL, but when "a website is blocked" (from the text of the previous URL), we should go to 5XX, as in 503 - service unavailable.
Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
21–30 of 93 posts
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#22Earlier quoted context omitted.
Change the default meaning of 403? I don't think that's a good idea. When a user needs to be logged in to do something and they aren't, you show them 403. When access is restricted to people outside a network, they see 403. It'll be hard to force a new behaviour onto the existing web, easier to add a new HTTP code.
My understanding is that the server should respond with 401 Unauthorized when someone is attempting to access a resource that requires authentication. What is the case for using 403 instead?
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#23Earlier quoted context omitted.
Change the default meaning of 403? I don't think that's a good idea. When a user needs to be logged in to do something and they aren't, you show them 403. When access is restricted to people outside a network, they see 403. It'll be hard to force a new behaviour onto the existing web, easier to add a new HTTP code.
My understanding is that the server should respond with 401 Unauthorized when someone is attempting to access a resource that requires authentication. What is the case for using 403 instead?
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#24The whole point of this is wrong... The internet is free, content shouldn't be blocked for legal reasons
I agree with your sentiment though - the internet _should_ be free.
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#25Seems like a good idea, but the wrong way to achieve it. The right way, as I understand it, would be to write it up as an RFC and submit it to the IETF; and to contribute code for it to some of the popular web servers (apache, nginx, etc). The site doesn't make any mention of either of those things. Edit: oops, I was wrong. There is an RFC and it's linked from http://www.451unavailable.org/what-is-error-451/
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#26Technically speaking 403 can be returned if it's blocked for legal reasons, but obviously it would be nice to know why it is forbidden.
There is some reasoning about this on: http://www.451unavailable.org/why-do-we-need-error-451 Still, imho, 4XX could be a response for a given URL, but when "a website is blocked" (from the text of the previous URL), we should go to 5XX, as in 503 - service unavailable.
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#27Technically speaking 403 can be returned if it's blocked for legal reasons, but obviously it would be nice to know why it is forbidden.
There is some reasoning about this on: http://www.451unavailable.org/why-do-we-need-error-451 Still, imho, 4XX could be a response for a given URL, but when "a website is blocked" (from the text of the previous URL), we should go to 5XX, as in 503 - service unavailable.
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#28Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#29Messages to their volunteer address get a vacation message that they're away until September 1st.
Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons
#30Earlier quoted context omitted.
There is some reasoning about this on: http://www.451unavailable.org/why-do-we-need-error-451 Still, imho, 4XX could be a response for a given URL, but when "a website is blocked" (from the text of the previous URL), we should go to 5XX, as in 503 - service unavailable.
5xx does not really make sense for a single page removed due to DMCA.