Why? There was no bug!

Not all serves include wget by default, but curl is part of the standard package set.

Why? There was no bug!

You have tested currency update using hosting Cron?

Why? There was no bug!

You have tested currency update using hosting Cron?

Yes, works fine on our webhost.

With?

wget -q "ecb_url" >/dev/null 2>&1

@condor2 try saying what error you get when you do that...

@condor2 try saying what error you get when you do that...

Using wget will download a bunch of 0 kb files on server.

index.php?route=extension%2Fcurrency%2Fecb%2Frefresh
index.php?route=extension%2Fcurrency%2Fecb%2Frefresh.1
index.php?route=extension%2Fcurrency%2Fecb%2Frefresh.2

So that is 2 good reasons to switch to curl in favor of wget.

• wget can leave clutter on the server
• wget is not available on all server configurations

You are quick coming to the wrong conclusion. The original call was a simple

wget -q "https://www.your-domain.com/index.php?route=extension/currency/ecb/refresh"

for the CRON task, and it works perfectly fine, without generated zero-bytes files.

What webhost doesn't have wget ? This one of the most common Linux/Unix commands available on webhosts.

If you want to submit pull-requests for bugfixes, you are welcome, but please do some proper testing first, or at least provide some explanations.

You are quick coming to the wrong conclusion. The original call was a simple

wget -q "https://www.your-domain.com/index.php?route=extension/currency/ecb/refresh"

I have tested before. On my server download/generate zero-bytes files. so thats why I have tried with >/dev/null 2>&1, but same.

So I use curl -s without zero-bytes files, but feel free to change back to wget -q

According to wget --help:

GNU Wget 1.20.3, a non-interactive network retriever.
Usage: wget [OPTION]... [URL]...
....
-q,  --quiet                     quiet (no output)
....

So ask your webhost to fix your wget then, we have run this command on countless servers/webhosts, never had this issue.

You are quick coming to the wrong conclusion.

You are quick to dismiss a problem with out understanding it.

The original call was a simple wget -q

Now it's curl -s, I don't see how one is simpler then the other, they are the exact same number and type of symbols.

wget -q "https://www.your-domain.com/index.php?route=extension/currency/ecb/refresh"

for the CRON task, and it works perfectly fine, without generated zero-bytes files.

Which vendor is your wget from? It could be a different between for example the BusyBox and GNU implementation.

What webhost doesn't have wget ? This one of the most common Linux/Unix commands available on webhosts.

Lots. curl is part of the ubuntu-server meta package, wget is not, minimalistic setups based on ubuntu-server would be setup like that.

please do some proper testing first

What is it that wasn't tested here?

According to wget --help:

GNU Wget 1.20.3, a non-interactive network retriever.
Usage: wget [OPTION]... [URL]...
....
-q,  --quiet                     quiet (no output)
....

So ask your webhost to fix your wget then, we have run this command on countless servers/webhosts, never had this issue.

You are misunderstanding that description, "quiet (no output)" means nothing is printed on stdout, not that it will not generate a file. This is used to avoid clutter in the server logs, not to have it not save the downloaded file. I'm starting to think you are the one that didn't test this.

To prevent wget from saving a file you need to give it something wget -O /dev/null URL.

@AlenJo: OK, you right, the wget should indeed use the -q --no-check-certificate -O /dev/null . I stand corrected here!