Live data from Hacker News

Campaign for a new HTTP Error code: 451 - Blocked for legal reasons

451unavailable.org

61–70 of 93 posts

Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons

#64

Earlier quoted context omitted.

Disclaimer: I work for an ISP and every ISP in Russia is legally required to do the censorship (and mirror all traffic to FSB black boxes, but that's another story). I'm not partucilarly happy with the situation, but can't do anything about that. Nginx is totally relevant as many ISPs including our use GNU/Linux boxes running Nginx as a highly performant transparent proxy (there are TPROXY patches for Nginx) to dive…

> I work for an ISP and every ISP in Russia is legally required to do the censorship (and mirror all traffic to FSB black boxes, but that's another story). I hate the censorship but I like the fact you're not gagged and can talk about the fact traffic is being mirrored.

OR, he's not allowed to, and he's doing it anyway.

Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons

#65

Surprised no one has made any reference to Farenheit 451. Allow me to be the first. Thankfully websites are not flammable.

The error code for censorship is the reference. I guess not everyone would recognize that, but I immediately noticed.

Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons

#66
post #3

Well, the cool thing about HTTP error codes is that you don't need a campaign or get permission from the W3C, you can just start using them if you want.

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.

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.

You mean like this? https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custo...

Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons

#67
post #28

Surely this should be within the 5xx range of status codes? I get there's a reference to be had using 451 but this is more of a server error than client.

No, I'd say it's a 4xx error. Have a look at https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Usually, 5xx means that the client could retry the request at a later time, and have it succeed. 4xx means the client should expect the request to fail forever unless something is changed.

Some HTTP clients (not browsers, but other things) take advantage of this by showing the user an error dialog on a 4xx error, but just retry at a later time on a 5xx error.

Re: Campaign for a new HTTP Error code: 451 - Blocked for legal reasons

#70

Earlier quoted context omitted.

Since the sites blocked on ISP level code contribution to apache/nginx or other web servers is irrelevant.

Disclaimer: I work for an ISP and every ISP in Russia is legally required to do the censorship (and mirror all traffic to FSB black boxes, but that's another story). I'm not partucilarly happy with the situation, but can't do anything about that. Nginx is totally relevant as many ISPs including our use GNU/Linux boxes running Nginx as a highly performant transparent proxy (there are TPROXY patches for Nginx) to dive…

Given that Russia appears to be engaged in even broader surveillance and monitoring than the U.S., I find it odd that Snowden would be granted temporary asylum there for speaking out about a similar program in the U.S. It makes the whole situation look more like a political game.
Post reply on HN