{"id":12861,"date":"2019-12-06T07:45:28","date_gmt":"2019-12-06T06:45:28","guid":{"rendered":"https:\/\/daniel.haxx.se\/blog\/?p=12861"},"modified":"2019-12-06T07:45:28","modified_gmt":"2019-12-06T06:45:28","slug":"curl-speaks-etag","status":"publish","type":"post","link":"https:\/\/daniel.haxx.se\/blog\/2019\/12\/06\/curl-speaks-etag\/","title":{"rendered":"curl speaks etag"},"content":{"rendered":"\n

The ETag<\/code><\/strong> HTTP response header is an identifier for a specific version of a resource. It lets caches be more efficient and save bandwidth, as a web server does not need to resend a full response if the content has not changed. Additionally, etags help prevent simultaneous updates of a resource from overwriting each other (“mid-air collisions”<\/a>).<\/p><\/blockquote>\n\n\n\n

That’s a quote from the mozilla ETag documentation<\/a>. The header is defined in RFC 7232<\/a>.<\/p>\n\n\n\n

In short, a server can include this header when it responds with a resource, and in subsequent requests when a client wants to get an updated version of that document it sends back the same ETag and says “please give me a new version if it doesn’t match this ETag anymore”<\/em>. The server will then respond with a 304 if there’s nothing new to return.<\/p>\n\n\n\n

It is a better way than modification time stamp to identify a specific resource version on the server.<\/p>\n\n\n\n

ETag options<\/h2>\n\n\n\n

Starting in version 7.68.0 (due to ship on January 8th, 2020), curl will feature two new command line options that makes it easier for users to take advantage of these features. You can of course try it out already now if you build from git<\/a> or get a daily snapshot<\/a>.<\/p>\n\n\n\n

The ETag options are perfect for situations like when you run a curl command in a cron job to update a file if it has indeed changed on the server.<\/p>\n\n\n\n

--etag-save <filename><\/code> <\/h3>\n\n\n\n

Issue the curl command and if there’s an ETag coming back in the response, it gets saved in the given file.<\/p>\n\n\n\n

--etag-compare <filename><\/code> <\/h3>\n\n\n\n

Load a previously stored ETag from the given file and include that in the outgoing request (the file should only consist of the specific ETag “value” and nothing else). If the server deems that the resource hasn’t changed, this will result in a 304 response code. If it has changed, the new content will be returned.<\/p>\n\n\n\n

Update the file if newer than previously stored ETag:<\/p>\n\n\n\n

curl --etag-compare etag.txt --etag-save etag.txt https:\/\/example.com -o saved-file<\/pre>\n\n\n\n
If-Modified-Since options<\/h2>\n\n\n\n
The other method to accomplish something similar is the -z<\/a> (or --time-cond<\/code>) option. It has been supported by curl since the early days. Using this, you give curl a specific time that will be used in a conditional request. “only respond with content if the document is newer than this”:<\/p>\n\n\n\n
curl -z \"5 dec 2019\" https:\/example.com<\/pre>\n\n\n\n
You can also do the inversion of the condition and ask for the file to get delivered only if it is older than a certain time (by prefixing the date with a dash):<\/p>\n\n\n\n
curl -z \"-1 jan 2003\" https:\/\/example.com<\/pre>\n\n\n\n
Perhaps this is most conveniently used when you let curl get the time from a file. Typically you’d use the same file that you’ve saved from a previous invocation and now you want to update if the file is newer on the remote site:<\/p>\n\n\n\n
curl -z saved-file -o saved-file https:\/\/example.com<\/pre>\n\n\n\n
Tool, not libcurl<\/h2>\n\n\n\n
It could be noted that these new features are built entirely in the curl tool by using libcurl correctly with the already provided API, so this change is done entirely outside of the library.<\/p>\n\n\n\n
Credits<\/h2>\n\n\n\n
The idea<\/a> for the ETag goodness came from Paul Hoffman. The implementation<\/a> was brought by Maros Priputen – as his first contribution to curl! Thanks!<\/p>\n","protected":false},"excerpt":{"rendered":"
The ETag HTTP response header is an identifier for a specific version of a resource. It lets caches be more efficient and save bandwidth, as a web server does not need to resend a full response if the content has not changed. Additionally, etags help prevent simultaneous updates of a resource from overwriting each other … Continue reading curl speaks etag<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":5,"featured_media":12136,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[33,230],"class_list":["post-12861","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-curl","tag-curl-and-libcurl","tag-http"],"_links":{"self":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/12861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/comments?post=12861"}],"version-history":[{"count":20,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/12861\/revisions"}],"predecessor-version":[{"id":12916,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/12861\/revisions\/12916"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/media\/12136"}],"wp:attachment":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/media?parent=12861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/categories?post=12861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/tags?post=12861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}