4 ms·

Doesn't it depend on a lot of things? For example you can only do head requests to see if a page changed since a given timestamp. If not then there is no need t

• JCharante 6y ago
  For anybody wondering how: The HTTP HEAD method requests the headers that would be returned if the HEAD request's URL was instead requested with the HTTP GET method. For example, if a URL might produce a large download, a HEAD request could read its Content-Length header to check the filesize without actually downloading the file. https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HE...
  • JimDabell 6y ago
    Typically you wouldn’t bother with a HEAD request, you’d do a conditional GET request. When you request a page, the response includes metadata, usually including a Last-Modified timestamp and often including an ETag (entity tag). Then when you make subsequent requests, you can include these in If-Modified-Since and If-None-Match request headers. If the resource hasn’t changed, then the server responds with 304 Not Modified instead of sending the resource all over again. If the resource has changed, then the server sends it straight away. Doing it this way means that in the case where the resource has changed, you make one request instead of two, and it also avoids a race condition where the resource changes between the HEAD and the GET requests.
    • JCharante 6y ago
      Do a lot of random pages return etags? I've only ever seen them in the AWS docs for boto3
      • account42 6y ago
        nginx sends it by default for static files (example: hacker news [0]), I assume other web servers do too. [0] https://news.ycombinator.com/y18.gif https://news.ycombinator.com/y18.gif