Hi Levander!
I am not an expert by any means, just another user,
but what does the -E option do for you?
-E = --html-extension
apache. Could wget, for url's that end in slashes, read the
content-type header, and if it's text/xml, could wget create index.xml
inside the directory wget
Hi all,
is there a fix when file names are too long?
Example:
On Mon, 21 Mar 2005, Martin Trautmann wrote:
is there a fix when file names are too long?
bash-2.04$ wget -kxE $URL
--15:16:37--
Hello
all:
Here
is the scenario... I am trying to d/l a webpage, but the issue is there are two
authentication challenges. The first is from the web server, so I wanted to use
something like wget
--http-user=user --http-passwd=password http://website.html , once authenticated with the
On 2005-03-21 15:32, [EMAIL PROTECTED] wrote:
*** This is not problem of wget, but your filesystem. Try to do
touch
Martin Trautmann [EMAIL PROTECTED] writes:
is there a fix when file names are too long?
I'm afraid not. The question here would be, how should Wget know the
maximum size of file name the file system supports? I don't think
there's a portable way to determine that.
Maybe there should be a way
The --post-data option was added in version 1.9. You need to upgrade your
version of wget.
Tony
-Original Message-
From: Richard Emanilov [mailto:[EMAIL PROTECTED]
Sent: Monday, March 21, 2005 8:49 AM
To: Tony Lewis; [EMAIL PROTECTED]
Cc: wget@sunsite.dk
Subject: RE: help!!!
wget
Martin Trautmann [EMAIL PROTECTED] writes:
On 2005-03-21 17:13, Hrvoje Niksic wrote:
Martin Trautmann [EMAIL PROTECTED] writes:
is there a fix when file names are too long?
I'm afraid not. The question here would be, how should Wget know the
maximum size of file name the file system
On Monday 21 March 2005 02:22 pm, Richard Emanilov wrote:
Guys,
Thanks so much for your help, when running
wget --http-user=login --http-passwd=passwd
--post-data=login=loginpassword=passwd https://site
With version 1.9.1, I get the error message
Site: Unsupported scheme.
have you
/usr/local/bin/wget -dv --post-data=login=loginpassword=password
https://login:[EMAIL PROTECTED]:8443/ft
DEBUG output created by Wget 1.9.1 on linux-gnu.
--17:11:35-- https://login:[EMAIL PROTECTED]:8443/ft
= `ft'
Connecting to ip... connected.
Created socket 3.
Releasing 0x8123110
I'm not longer seeing the 401 error, I am now seeing
HTTP request sent, awaiting response... HTTP/1.1 501 Not Implemented
I need to end this nightmare!
Richard Emanilov
[EMAIL PROTECTED]
-Original Message-
From: Richard Emanilov
Sent: Monday, March 21, 2005 5:17 PM
To:
11 matches
Mail list logo