from the well,-there's-a-surprise dept
Two years ago, Techdirt reported on a very troubling ruling in the UK courts that BT had to block access to the Usenet service provider Newzbin2. At the time, many feared that this would be the thin end of the wedge, giving copyright companies an easy way to shut down other sites. And with that power, of course, would come the inevitable errors, blocking completely unrelated sites. Just how seriously those mistakes could be is shown by this recent case of massive overblocking, reported here on PC Pro:
Virgin Media and Sky-owned Be Broadband customers found they were unable to access the Radio Times website last week, after the ISPs' anti-piracy filters included the site by accident. Telefonica, which still runs Be Broadband's network said that the overblocking had actually affected around 200 legitimate websites.
Radio Times is a well-known UK TV and radio listings magazine; another major site affected was the citizen science project Zooniverse. As an Open Rights Group (ORG) post explains, the specific Radio Times address that was blocked was radiotimes.com, while www.radiotimes.com continued to function. Here's why:
Many third-party load balanced systems, for example those using Amazon's AWS [Amazon Web Services] infrastructure, are enabled by pointing CNAME records at names controlled by those third-party systems. For example www.example.com may be pointed at loadbalancer.example.net. However, "example.com" usually cannot be directly given a CNAME record (CNAME records cannot be mixed with the other record types needed such as those pointing to nameservers and mailservers). A common approach is to point "example.com" to a server that merely redirects all requests to "www.example.com".
As ORG surmised, the problem arose from a UK court decision handed down last month that allowed the Football Association Premier League Limited to block FirstRow Sports, a site for live-streaming sports events. It turned out that the latter used the redirection service http-redirection-a.dnsmadeeasy.com, which was then blocked as part of the court order. Unfortunately, hundreds of other sites, which also used that redirection service, were also blocked as a result.
From forum posts we can see that it's this redirection system, in this specific case an A record used for "http-redirection-a.dnsmadeeasy.com", that has been blocked by the ISPs -- probably a court-order-blocked site is also using the service -- making numerous sites unavailable for any request made without the "www" prefix.
This is a classic case of overblocking, but on a scale hitherto unseen in the UK. It shows why such Web blocks are very crude instruments, and how easily they can go wrong for quite subtle technical reasons. The problem is that the companies seeking the blocks can make mistakes, but the ISPs implementing the blocks don't want to become responsible for checking that the blocks are correct, and thus implement whatever is sent to them.
A post on the Zooniverse blog explains why this is so problematic:
The fact that the court could issue an order which didn’t see this coming and that the ISPs would act on it without checking that what they were doing was sensible is, in my opinion, extremely worrying. It shows how little power we as operators of a website have -- there are no guarantees that our hard work will travel along the little tubes that make up the internet to make it to your computer, and -- although Virgin were nice in this case -- it's disturbing to think we would have had no redress had they decided to keep blocking us. In the midst of a huge political argument in the UK about filtering content online, it's worth bearing in mind how a simple attempt by a multi-billion pound business to protect its revenue stream ended up, by complete and careless accident, preventing science getting done at the Zooniverse.
Sadly, we can probably expect things to get worse, as copyright companies resort to this approach more often, more mistakes are made, and more overblocks occur with little concern for the damage they cause.