Bug 684818

Summary:	Wget doesn't respect -np (no parent) option
Product:	Red Hat Enterprise Linux 6	Reporter:	David Jaša <djasa>
Component:	wget	Assignee:	Karsten Hopp <karsten>
Status:	CLOSED DEFERRED	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.2
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-20 13:36:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Jaša 2011-03-14 15:21:49 UTC

Description of problem:
When invoked with -np option, wget shouldn't download any files that are above specified directory, but wget in RHEL 6 does exactly that

Version-Release number of selected component (if applicable):
wget-1.12-1.4.el6.x86_64

How reproducible:
always with specified build

Steps to Reproduce:
1. run wget -np example.com/path/to/directory
2.
3.
  
Actual results:
wget also downloads files from example.com/path/to/another/directory

Expected results:
wget should only download files from example.com/path/to/directory

Additional info:

Comment 3 RHEL Program Management 2011-03-14 15:38:28 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 Karsten Hopp 2011-04-20 13:36:54 UTC

wget -np works reliably only with ftp urls, see 
http://savannah.gnu.org/bugs/index.php?20519 for an explanation.
Upstream is aware of this problem, but no fix is available yet. 
The suggested workaround atm. is to add a / at the end of the URL.