Handle 416 HTTP response codes properly

[pmonks]

Currently unfurl blindly issues an HTTP range request without checking if the server supports them or not. Although servers are supposed to return the full content with a 200 status code if they do not support HTTP range requests, some return a 416 status code instead, and in these cases unfurl should retry the request without the Range header.

(see also the discussion in issue #6)