Bug 684818 - Wget doesn't respect -np (no parent) option
Summary: Wget doesn't respect -np (no parent) option
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: wget
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Karsten Hopp
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-14 15:21 UTC by David Jaša
Modified: 2011-04-20 13:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-20 13:36:54 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.