RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1166699 - 0 return code when url missing scheme
Summary: 0 return code when url missing scheme
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: wget
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Jan Kepler
URL:
Whiteboard:
Depends On:
Blocks: 1373253
TreeView+ depends on / blocked
 
Reported: 2014-11-21 13:38 UTC by Justin Fay
Modified: 2017-03-21 10:14 UTC (History)
4 users (show)

Fixed In Version: wget-1.12-10.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 10:14:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Proposed patch (2.16 KB, text/plain)
2016-05-13 12:15 UTC, Zdenek Dohnal
no flags Details
Proposed patch (2.16 KB, patch)
2016-05-13 12:34 UTC, Zdenek Dohnal
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0661 0 normal SHIPPED_LIVE wget bug fix update 2017-03-21 12:34:04 UTC

Description Justin Fay 2014-11-21 13:38:43 UTC
Description of problem:

wget is returning a 0 return code when calling wget with a url containing no scheme

Version-Release number of selected component (if applicable):

GNU Wget 1.12 

How reproducible:
reproducible

Steps to Reproduce:
1. wget /foo/bar
2. echo $?

Actual results:
0

Expected results:
1

Additional info:
Fixed in later versions of wget

Comment 4 Zdenek Dohnal 2016-04-28 13:43:52 UTC
I looked into the code of this old version of Wget and I compared it with latest version, so I found out where the problem is. Global variable final_exit_status from file exits.c has still value of WGET_EXIT_SUCCESS, because at file main.c there is not any call of function inform_exit_status, which changes value of this variable according of error code. So proposed patch is to insert function call:

inform_exit_status(URLERROR);

on the line 1273 at main.c and to delete command:

status = URLERROR;

Comment 5 Zdenek Dohnal 2016-05-13 12:15:34 UTC
Created attachment 1157091 [details]
Proposed patch

Comment 6 Zdenek Dohnal 2016-05-13 12:34:32 UTC
Created attachment 1157110 [details]
Proposed patch

Comment 14 errata-xmlrpc 2017-03-21 10:14:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0661.html


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