[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-wget] Timestamping and --continue

From: Jack Bates
Subject: [Bug-wget] Timestamping and --continue
Date: Wed, 20 Mar 2019 11:36:31 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0

When combined with the --continue option, should --timestamping send an If-Unmodified-Since header?

Currently, if I partially download a file and then run `wget --debug --continue --timestamping URL` I get:

---request begin---
GET [...] HTTP/1.1
If-Modified-Since: Tue, 13 Nov 2018 14:13:29 GMT
Range: bytes=1084899556-

---response begin---
HTTP/1.1 304 Not Modified

---response end---
304 Not Modified
File ‘[...]’ not modified on server. Omitting download.

and I'm left with the still-incomplete file 😞

If Wget instead sent If-Unmodified-Since, I'd expect it to resume downloading:

---response begin---
HTTP/1.1 206 Partial Content

---response end---
206 Partial Content
Length: [...], [...] remaining
Saving to: ‘[...]’

If the file was already complete, I'd expect:

---response begin---
HTTP/1.1 416 Requested Range Not Satisfiable

---response end---
416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.

And if the file was out of date (complete or otherwise), I'd expect:

---response begin---
HTTP/1.1 412 Precondition Failed

---response end---
412 Precondition Failed

reply via email to

[Prev in Thread] Current Thread [Next in Thread]