Hi,
thanks for that link again, Fernando (I had misplaced my note on it:-)
And now I wonder if anyone has ported wget2 to Windows?
Thanks,
Gerd
- Original Message -
From: "Fernando Cassia"
To: "ENG WKJC"
Cc: "bug-wget"
Sent: Wednesday, October 25, 2023 1:14:17 AM
Subject: Re:
Functioning as designed ...
(Disclaimer: I am not an expert user of this program, but I have some
experience that may help you:)
I guess you are Windows users. Unlike Unix and Linux systems, in Windows the
last part of a file name (anything following the last ("rightmost") period is
Hi,
could it be that you were trying to specify an output file by using the "-o"
option and by mistake entered a "-0" (dash Zero instead of dash lowercase O) ?
Regards,
Gerd (not one of the resident experts here ;-)
- Original Message -
From: "Dalingcebo Dlamini"
To: "bug-wget"
Even TLS 1.2 is not quite "current" - it dates back to 2008, TLS 1.3 was
published in 2018.
Quoting wikipedia:
Website protocol support (as per May 2022)
Protocol
version Website
support[87] Security
SSL 2.0 0.3%Insecure
SSL 3.0 2.5%Insecure
TLS 1.0
To: "Tim Ruehsen" , ge...@mweb.co.za
Cc: "bug-wget" , "darnir"
Sent: Tuesday, May 31, 2022 2:35:41 PM
Subject: Re: wget-1.21.3-win32/64
Hi,
I just tested the wget2 executable on my Win10 with exactly the same command :
wget2.exe -O TargetPath\TargetFile [ http://
from 2016.)
There is a possibility that someone found it useful to fix that -O behaviour
and just did it.
2) the errant behaviour of the Netgear - I assume there are no software fixes
for this?
Regards,
Gerd
- Original Message -
From: "WQ"
To:
Hi,
I am not normally concerned with solving issues surrounding wget, but I use it
a lot myself (mostly on Windows, like you) so the problem you describe
intrigues me.
I don't use a NAS, so I can only assume that both of yours (as well as your yet
unknown next one) would use some form of
(not sure if reply all is appropriate here)
I tried this from South Africa and I am getting the exact behaviour as the OP.
I tried a referer and a user agent as from my browser (a well-aged Firefox),
without changing the result.
(fwiw: The downloaded audio sounds Italian to me.)
Of course,
It seems to me that in the command
wget -0 install-nethunter-termux https://offs.ec/2MceZWr
that is a "zero" there where the -o parameter ought to be.
Sending us the help output rather than studying it and hunting for the error
oneself is indeed not a very good strategy ...
As for the
Hi,
I see. Fascinating story. But it probably then is too late to fix that issue
now (old wget, old servers, old antivirus on old router - they are all possible
sources of errors.)
Also, as was pointed out here by others (was it Tim?) as well as me: The
continuation mechanism by its very
- Forwarded Message -
From: ge...@mweb.co.za
To: "Tim Ruehsen"
Sent: Friday, January 21, 2022 1:59:41 PM
Subject: Re: Wget
I happen to have an old XP with a wget 1.9.1 installed (and used a lot in its
day), which, I presume predates the 1.11.4 (9 < 11 if numeric?)
Hi,
not being a wget fundi - there are lots out here that are better with this - I
have a different suspicion:
if you have wget installed in what I suspect is c:\windows\system32\ and you
run your command from that directory then wget will try to place the downloaded
files in that directory
Interesting - forcing a user agent string could be in violation of GDPR since
it would definitely make the user environments more identifiable. The
"fingerprinting" discussion refers. On the other hand, if all browsers
henceforth were to send the same string the opposite would be true.
I
Hi guys,
I just checked, I believe the version of wget I am running is from 2003 (and I
have been using it for much mich longer than that ...) At some point I even
wrote scripts around wget batch jobs I used to run ...
But I am kind of stuck in Windows. And things happen on a different time
14 matches
Mail list logo