On Wed, 20 Apr 2005, Hrvoje Niksic wrote:
It seems this site is sending something that the OpenSSL library cannot
handle. For example, both Wget and curl on Linux display the same error:
$ curl https://www.danier.com
curl: (35) error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or
Ola!
I encountered a problem on Win XP when I want to use -m option with wget.
The command looks like this : wget -m -nH -nv -o wget.log --cut-dirs=1
--progress=bar http://IP_ADDRESS:8014/VIRTUAL_DIR
Directory structure on server looks something like this and inside every
directory there is one
Hello gnu,
I'm experiencing a wrong display of the file size of a huge file to get:
berny wget -Y off -c 'ftp://my-server/pub/dvd.iso'
--13:56:35-- ftp://my-server/pub/dvd.iso
= `dvd.iso'
Resolving my-server... 192.168.0.4
Connecting to
Hi!
Last two days I have been learning and debugging NTLM on the latest
version of wget from cvs (1.10-alpha2+cvs-dev). Mainly I have debugged
on linux, but noticed same problems occurs on win32 too. During testing
I found four bugs, that needs to be fixed.
On previous threads I noticed that
Wget 1.9.1 doesn't work with large files. The soon-to-be-released
1.10 does, though.
ftp://ftp.deepspace6.net/pub/ds6/sources/wget/wget-1.10-alpha2.tar.bz2
Sami Krank [EMAIL PROTECTED] writes:
Last two days I have been learning and debugging NTLM on the latest
version of wget from cvs (1.10-alpha2+cvs-dev). Mainly I have
debugged on linux, but noticed same problems occurs on win32
too. During testing I found four bugs, that needs to be fixed.
On Thu, 21 Apr 2005, Konrad Chan wrote:
After browsing the openssl newsgroup per Hrvoje's suggestion, I came to a
similar conclusion as well (cipher problem). However, I couldn't find
instructions on how to change the cipher for wget, I tried all the different
ciphers using curl but no luck,
Daniel Stenberg [EMAIL PROTECTED] writes:
On Thu, 21 Apr 2005, Konrad Chan wrote:
After browsing the openssl newsgroup per Hrvoje's suggestion, I came
to a similar conclusion as well (cipher problem). However, I
couldn't find instructions on how to change the cipher for wget, I
tried all
On Wed, 20 Apr 2005, Hrvoje Niksic wrote:
Herold Heiko [EMAIL PROTECTED] writes:
I am greatly surprised. Do you really believe that Windows users
outside an academic environment are proficient in using the compiler?
I have never seen a home Windows installation that even contained a
Doug Kaufman [EMAIL PROTECTED] writes:
On Wed, 20 Apr 2005, Hrvoje Niksic wrote:
Herold Heiko [EMAIL PROTECTED] writes:
I am greatly surprised. Do you really believe that Windows users
outside an academic environment are proficient in using the compiler?
I have never seen a home Windows
I remembered why I never documented the SSL options. Because they are
badly named, accept weird values, and I wanted to fix them. I felt
(and still feel) that documenting them would make them official and
force us to keep supporting them forever.
Here is the list, extracted from `wget --help':
Hrvoje Niksic wrote:
The question is what should we do for 1.10? Document the
unreadable names and cryptic values, and have to support
them until eternity?
My vote is to change them to more reasonable syntax (as you suggested
earlier in the note) for 1.10 and include the new syntax in the
I'm setting up a site for my company to allow
people to get certain files out of our company repository. Basically, I
want people to be able to write the following:
wget http://servername/~tgibbs/FileWanted.rpm
However, the files are stored someplace else and I
don't want to mirror them.
Hi!
You may use this server to test NTLM-authentication on wget.
http://212.50.205.135/ntlm/
usr: testuser
pwd: DummyUser
Server is not promised to be available all the time, because
it is actually running under my linux workstation.
Server is MS Windows Server 2003
14 matches
Mail list logo
