You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It turns out that some servers don't fully support the HEAD method, and instead of returning the same status code as they would for get, they return something different like 404 or 500.
We cannot, therefore, rely on the HEAD request to give us useful information about the link and instead make a GET request. This does pose the problem of downloading unnecessarily large files, so some investigation needs to be made into whether it's possible to fake a HEAD request by terminating the connection as the content starts to come through.
The text was updated successfully, but these errors were encountered:
It turns out that some servers don't fully support the
HEAD
method, and instead of returning the same status code as they would for get, they return something different like 404 or 500.We cannot, therefore, rely on the
HEAD
request to give us useful information about the link and instead make aGET
request. This does pose the problem of downloading unnecessarily large files, so some investigation needs to be made into whether it's possible to fake aHEAD
request by terminating the connection as the content starts to come through.The text was updated successfully, but these errors were encountered: