Re: [Bug-wget] Wget 1.20.3 timestamp behavior doesn't match the one described on the manual

2019-08-15 Thread Dalme
On 15/08/19 14:32, Tim Rühsen wrote: > On 8/15/19 2:23 PM, Dalme wrote: >>> Are you saying that wget sends a wrong date with the If-Modified-Since >>> header ? If so it's a bug on our side. Maybe you can come up with more >>> details (--debug output). >> No, sorry. What I'm trying to say is

Re: [Bug-wget] Wget 1.20.3 timestamp behavior doesn't match the one described on the manual

2019-08-15 Thread Tim Rühsen
On 8/15/19 2:23 PM, Dalme wrote: > >> Are you saying that wget sends a wrong date with the If-Modified-Since >> header ? If so it's a bug on our side. Maybe you can come up with more >> details (--debug output). > No, sorry. What I'm trying to say is that when you take a look on the > wget manual

Re: [Bug-wget] Wget 1.20.3 timestamp behavior doesn't match the one described on the manual

2019-08-15 Thread Dalme
> Are you saying that wget sends a wrong date with the If-Modified-Since > header ? If so it's a bug on our side. Maybe you can come up with more > details (--debug output). No, sorry. What I'm trying to say is that when you take a look on the wget manual at gnu.org of '-N' mode you find "Turn

Re: [Bug-wget] Wget 1.20.3 timestamp behavior doesn't match the one described on the manual

2019-08-15 Thread Tim Rühsen
On 8/14/19 9:07 PM, Dalme wrote: > From the wget manual (at > https://www.gnu.org/software/wget/manual/wget.html#Time_002dStamping): > "If the local file does not exist, or the sizes of the files do not > match, Wget will download the remote file no matter what the time-stamps > say." However,