Re: --etag-compare vs. --time-cond
Paul Gilmartin via curl-users <[email protected]>
| Newsgroups | gmane.comp.web.curl.general |
|---|---|
| Message-ID | <[email protected]> |
On 3/4/23 13:59:42, Timothe Litt via curl-users wrote: > On 04-Mar-23 15:12, Paul Gilmartin via curl-users wrote: >> If I specify both --etag-compare and --time-cond and they disagree on >> whether a file is up-to-date, which wins? >> >> (It might depend on the HTTPD) > > RFC 7232 <https://www.rfc-editor.org/rfc/rfc7232> Section3.3 specifies that the E-Tag wins for GET class requests. Thanks. So in a test I (caused to be) supplied: > If-Modified-Since: Sat, 04 Mar 2023 21:52:30 GMT > If-None-Match: wombat # I'm guessing this does *NOT* match ... and got: < HTTP/1.1 304 Not Modified < Last-Modified: Thu, 17 Nov 2022 02:01:41 GMT ... apparently the If-None-Match: did not dominate. But this man mean only that the HTTPD violates RFC 7232. -- Thanks again, gil -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.html