Re: [Bug-wget] Unexpected wget -N behaviour for 1.17 onwards?

[Tim Rühsen]

Hi Lawrence,

thank you for having so much trust in us :-)

But don't forget, 'us' is the community, not only the maintainers.
You and your interactions are also an important and driving part of the
OSS community. Wget is also "your Wget".

Regards, Tim

On 2/11/19 9:38 PM, Lawrence Wade wrote:
> On Mon, Feb 11, 2019 at 7:29 AM Tim Rühsen <address@hidden> wrote:
>> You are right, --if-modified-since changes -N behavior in case a file is
>> incomplete. --if-modified-since can't easily be fixed since the 304
>> response does not include file size information.
> 
> You're the expert on HTTP servers and their responses. I bow to you
> and your superior knowledge. At least in my usage case (and countless
> scripts, etc) this will break expected functionality. Though I applaud
> the goal.
> 
> Hey, I'm a hardware guy, my programming style is so much brute force
> and ignorance that a naMeleSs company once offered me a job to work on
> Outlook Express. I'm not a programmer, I use bubble sorts! (But if you
> want to use car alternators as the steppers in your huge 3D printer,
> e-mail me.)
> 
>> As you suggest, we should disable this option by default or at least
>> discuss the options we have.
> 
> The default behaviour should be that $ wget -r -N www.host.com checks
> file sizes first and revision dates second, as it has appeared to work
> for the 20+ years I've been using wget.
> 
> But how to implement new efficiencies and great ideas without breaking
> existing functionality? I'll test drive anything you or the rest of
> the wget developers write.
> 
> Thanks for taking me seriously and looking into it. This is why all my
> hardware proudly runs open-source software.
> 
> Thank you, everyone who is reading this. I appreciate your great work
> and the software you have made. wget is infrastructure to the
> functioning of the modern Internet.
> 
> Lawrence Wade
> Ottawa, Canada
>

signature.asc
Description: OpenPGP digital signature