On Sat, Feb 24, 2018 at 7:00 AM, <[email protected]> wrote:
> > Date: Sat, 24 Feb 2018 12:14:33 +0100 > From: Florian Balmer <[email protected]> > Subject: Re: [fossil-users] Minor Issues with Fossil 2.5dg_ > [email protected] > <cahgau9jjo9uy0qy%2bbf-0lj1wsk3wjmel%[email protected]>> > Content-Type: text/plain; charset="UTF-8" > > Thinking about HTTP caching twice, the following comes to my mind: > > A command line download tool, that unlike a web browser does not keep > a cache of content and associated ETags, won't be able to calculate > the ETag for a file it is going to request from a Fossil web server. > Someone already made an ETag wrapper for wget: https://www.w3.org/2001/12/rubyrdf/pack/tests/scutter/wget.pl If you aren't using Perl, call it like: perl wget.pl $filename > ETags are not simple file checksums, and Fossil seems to use the > following information to generate them: > > <mask><exec-mtime>/<data-or-config-key>/<cookie>/<hash> > There is no requirement or specification for the value of an ETag, could use the Fossil artifact hash as the ETag value. Then a script trying to fetch the file can generate the value from the current copy of the file.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
