Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

IETF mulls adding geoblock info to 'Bradbury's code'

Proposal to extend Error 451

After a long campaign, the Internet Engineering Task Force (IETF) has decided that users deserve to know why pages were blocked and created HTML error 451. Now the body will consider a proposal to extend it to give users more information.

“Error 451” entered the canon in December 2015, with the name honouring Ray Bradbury's “Fahrenheit 451” and a rationale that users deserved to know if legal constraints (such as censorship) were being applied to pages they wished to view.

The original spec provided only minimal information: if used, it would return a status code stating a resource was unavailable for legal reasons, and the response should include a reason.

One Shivan Kaul Sahib now thinks more information is needed, and is asking the IETF to expand the Error 451 with some new protocol elements.

His suggestions in this draft are that the protocol elements include:

  • A header field that identifies the “blocking authority”;
  • A response element that indicates to users if they're geo-blocked from a particular site.

The suggestions are the result of an implementation report that's been looking at Error 451 since it was adopted as a standard in February 2016.

That report, published in July 2017, noted that geoblocking was primarily associated with gambling sites.

There's another reason the IETF would consider encouraging the use of 451, and enhancing it: since it's machine readable, it provides a potentially-useful research tool (for example, to answer “how much content is blocked for reasons pertaining to intellectual property rights ?”), and it can be returned by encrypted Web pages. ®

Similar topics

TIP US OFF

Send us news


Other stories you might like