Bug #36138
closed
Invalid syntax for curl --time-cond
Added by Leos Stejskal about 2 years ago.
Updated about 2 years ago.
Description
According to Curl man page, syntax for --time-cond attribute
should be "--time-cond file <path>", not "--time-cond <path>".
This can cause issues with outdated vmlinuz and initrd.im files,
once the files are downloaded, they are never replaced with never versions.
[0] https://curl.se/docs/manpage.html
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/856 added
- Fixed in Releases 3.7.0 added
- Pull request https://github.com/theforeman/smart-proxy/pull/858 added
- Pull request https://github.com/theforeman/smart-proxy/pull/859 added
- Fixed in Releases 3.6.0 added
- Status changed from Ready For Testing to Closed
- Fixed in Releases 3.5.2 added
- Category set to Core
- Triaged changed from No to Yes
- Fixed in Releases deleted (
3.7.0)
Note that this has caused a regression, no new vmlinuz / initrd can be downloaded anymore after this change, see this report for more details:
https://projects.theforeman.org/issues/36209
In fact, the manpage linked here shows the example:
curl -z file https://example.com
i.e. the correct syntax is
--time-cond <path>, as can be confirmed via:
$ touch foo && curl --time-cond file foo https://redhat.com
Warning: Illegal date format for -z, --time-cond (and not a file name).
Warning: Disabling time condition. See curl_getdate(3) for valid date syntax.
curl: (6) Could not resolve host: foo
...
- Related to Bug #36209: tftp initrd/vmlinux generation: curl malformed added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by