Re: [Bug-wget] Please help to check this issue

[Li, Jian]

Hi,

Thanks for your reply. The attachment is debug log(added the --debug 
parameter). Please help to check.
Now I have two questions about WGET:
1. Why does WGET get the nonexistent paths? The folder isn't exist in page.
2. If the path is too long, there are many folder structures, can WGET download 
successfully? I have debug it, when the folder structures are too long and very 
complex, WGET downloads failed.


Thanks,
Li, Jian

-----Original Message-----
From: Darshit Shah [mailto:address@hidden 
Sent: Friday, May 23, 2014 10:01 PM
To: Li, Jian
Cc: address@hidden
Subject: Re: [Bug-wget] Please help to check this issue

Hi Li,

Could you please provide some more details about your use case so we can 
diagnose the issue?
Please provide us with the complete debug logs, generated by adding the --debug 
parameter to the Wget command line you're issuing.

However, I'm assuming that you're trying to download something recursively and 
the page references the above Styles.css file which does not exist.

On Fri, May 23, 2014 at 2:04 PM, Li, Jian <address@hidden> wrote:
> Hi Team,
>
> I meet an issue when I use wget to down our builds, but I can't find the 
> reason. Could you tell why?
>
> Our download path doesn't include the folder 
> "Resources/Stylesheets/Styles.css", but wget accesses this, so It displays 
> the following messages.
> I want to know the reason, why does wget access the nonexistent path?
> #############################################################
> utables/licenses/Resources/Stylesheets/Styles.css'
> Connecting to sham-2118-11.chn.hp.com|16.186.74.147|:8080... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 15:57:11 ERROR 404: Not Found.
> #############################################################
>
>
> Thanks,
> WGET user



--
Thanking You,
Darshit Shah