>What's the error you get?

It turns out >>2 actually works, but you have to preface the URL with the protocol http://