Re: «--etag-compare» while «--continue-at»
Date: Sat, 9 May 2020 15:47:12 -0400
On Sat, May 9, 2020 at 7:02 AM Jeremy Nicoll via curl-users
> On Sat, 9 May 2020, at 11:09, Коваленко Анатолий Викторович via curl-users wrote:
> > You asked an example. My script saved (as JSON) history of
> > HTTP-headers while downloading with
> > breaks of provider's connection.
> > Page: http://get.opera.com/ftp/pub/opera/desktop/68.0.3618.63/win/
> > File:
> > http://get.opera.com/ftp/pub/opera/desktop/68.0.3618.63/win/Opera_68.0.3618.63_Setup_x64.exe
> > Call: curl.exe -C - -D Dump.txt -O -R -y 10 -Y 1024 $HRef
> > You can see, that changed and restored for a short time (from
> > «05:12:42» to «08:19:29») values of
> > next parameters:
> > «ETag» (from «5ea97a29-38b5528» to «5ea97a2a-38b5528» and back);
> > «Last-Modified» (from «Wed, 29 Apr 2020 12:59:21 GMT» to «Wed, 29 Apr
> > 2020 12:59:22 GMT» and back);
> If the file being grabbed has changed while you've been trying to grab it,
> would this not make sense?
Also, some folks use etags to track users. It is another way to plant
a unique identifier on a user.
When etags are used as tracking cookies, then don't expect the
machinery to work as expected.
(I'm not sure if that is happening here, but it may explain some of
what is being seen).