On Sun, Feb 25, 2018 at 4:11 AM, <fossil-users-requ...@lists.fossil-scm.org> wrote:
> > Date: Sun, 25 Feb 2018 10:11:04 +0100 > From: Florian Balmer <florian.bal...@gmail.com > Subject: Re: [fossil-users] Minor Issues with Fossil 2.5 > > I think that the "Last-Modified" header is much easier to handle, as > it boils down to parsing a GMT date/time string. And, as already > mentioned, clobbering of locally-modified files can be avoided with > the timestamp mechanism, this is not possible with an ETag alone. > The ETag is supposed to only change when the content changes Therefore, if the Etag you have is not the same as the current ETag on the server - for the same resource - then the content is different. Admittedly, if the server's copy of the resource is changed to an older version, the ETag will be different, as well. So, if making you always need the newest version, then modification time is needed. But if different is acceptable, then Etag will do that.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
