I don't see the protocol specifier at the beginning of that url. They might be trying to catch people with certain unpatched browsers only reading the part of the URL after the first actual instance of "http://" in it. Currently, that leads to a 404, but it's always possible that that wasn't the case a day or so ago...