On Sun, Feb 25, 2018 at 7:00 AM,
wrote:
>
> Date: Sun, 25 Feb 2018 04:37:38 -0500
> From: Ron W
> Subject: Re: [fossil-users] Minor Issues with Fossil 2.5
>
> > Date: Sun, 25 Feb 2018 10:11:04 +0100
> > From: Florian Balmer
On 2/25/18, Florian Balmer wrote:
> As far as I remember, I've come across the recommendation to combine
> ETags and Last-Modified headers, so the client could pick
> If-None-Match or If-Modified-Since to validate its cached content.
>
> And, it's already there, and
D. Richard Hipp:
> Consider this sequence of operations:
>
> (1) User A does a "uv push"
> (2) User B does a "wget -N" against the uv.
> (3) User C does a "uv push" of different content.
>
> If all of (1), (2), and (3) happen during the same second and if
> unversioned content honors the
On 2/23/18, Florian Balmer wrote:
>
> 2. There's no "Last-modified" HTTP header when downloading unversioned
> files through the /uv web page, causing undesired network traffic for
> `wget -N' scripting scenarios,
Consider this sequence of operations:
(1) User A does a
On Sun, Feb 25, 2018 at 4:11 AM,
wrote:
>
> Date: Sun, 25 Feb 2018 10:11:04 +0100
> From: Florian Balmer Subject: Re: [fossil-users] Minor Issues with Fossil 2.5
>
> I think that the "Last-Modified" header is much easier to
Ron:
> Someone already made an ETag wrapper for wget:
> https://www.w3.org/2001/12/rubyrdf/pack/tests/scutter/wget.pl
Thanks for the interesting link.
> 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
>
6 matches
Mail list logo