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 676596 - [RFE] use reason phrase from HTTP status line in error messages
Summary: [RFE] use reason phrase from HTTP status line in error messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: curl
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Jiri Jaburek
URL:
Whiteboard:
Depends On:
Blocks: 840699
TreeView+ depends on / blocked
 
Reported: 2011-02-10 10:27 UTC by Petr Šplíchal
Modified: 2016-06-01 01:41 UTC (History)
6 users (show)

Fixed In Version: curl-7.19.7-30.el6
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 10:09:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0393 0 normal SHIPPED_LIVE curl bug fix and enhancement update 2013-02-20 20:51:32 UTC

Description Petr Šplíchal 2011-02-10 10:27:59 UTC 
Description of problem:

When an error is encountered, urlgrabber does not report a text
description of the problem any more, rather just gives the error
code. This is a regression comparing with RHEL5's urlgrabber.

Version-Release number of selected component (if applicable):
python-urlgrabber-3.9.1-7.el6.noarch

Steps to Reproduce:
Attempt to get a non-existent file or a file without a proper
authorization. For example:

urlgrabber http://www.redhat.com/g/
  

Actual results:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 403"

urlgrabber.grabber.URLGrabError: [Errno 14]
PYCURL ERROR 22 - "The requested URL returned error: 401"

urlgrabber.grabber.URLGrabError: [Errno 14]
PYCURL ERROR 22 - "The requested URL returned error: 404"


Expected results:
Here's how the error message look like on RHEL5:
urlgrabber.grabber.URLGrabError: [Errno 14] HTTP Error 403:
Forbidden

urlgrabber.grabber.URLGrabError: [Errno 14] HTTP Error 401:
Authorization Required

urlgrabber.grabber.URLGrabError: [Errno 14] HTTP Error 404:
Not Found
Comment 2 Petr Šplíchal 2011-02-10 10:59:27 UTC 
The different error format also causes the upstream test suite to
fail in the test_failure_callback subtest:

===============================================================================
FAIL: test that MG executes the failure callback correctly
-------------------------------------------------------------------------------

Traceback (most recent call last):
  File "test_mirror.py", line 120, in test_failure_callback
    '[Errno 14] HTTP Error 403')
  File "/tmp/tmp.p1OZ1Hz6jK/BUILD/urlgrabber-3.9.1/test/munittest.py", line 397, in failUnlessEqual
    (msg or '%s != %s' % (`first`, `second`))
AssertionError: '[Errno 14] PYCURL ERROR 2' != '[Errno 14] HTTP Error 403'

The test case should be adjusted to match the actual expected format.
Comment 3 James Antill 2011-02-10 21:22:00 UTC 
The testcases failing is known.

For the bug, do you have the fix for: 565654 ... also what is this a regression from, 6.0??
Comment 4 Petr Šplíchal 2011-02-14 09:06:01 UTC 
> For the bug, do you have the fix for: 565654

Yes, and the fix has already been verified:
https://bugzilla.redhat.com/show_bug.cgi?id=565654#c14

> ... also what is this a regression from, 6.0??

Against RHEL5.
Comment 6 James Antill 2011-08-16 19:08:57 UTC 
 This is basically the same bug as 565646, and it's already fixed for the same reasons ... if I run yum with a bad URL on 6.1 I get what you'd expect.

*** This bug has been marked as a duplicate of bug 565646 ***
Comment 7 Petr Šplíchal 2011-08-17 07:56:44 UTC 
Does not seem to be fixed. What I get is still just an error
number. I've tested python-urlgrabber-3.9.1-8.el6.noarch with the
following results:

> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :: [   LOG    ] :: http without credentials
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> 
> Traceback (most recent call last):
>   File "./grab.py", line 9, in <module>
>     urlgrab(url, filename)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 618, in urlgrab
>     return default_grabber.urlgrab(url, filename, **kwargs)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 985, in urlgrab
>     return self._retry(opts, retryfunc, url, filename)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 886, in _retry
>     r = apply(func, (opts,) + args, {})
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 971, in retryfunc
>     fo = PyCurlFileObject(url, filename, opts)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1066, in __init__
>     self._do_open()
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1360, in _do_open
>     self._do_grab()
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1490, in _do_grab
>     self._do_perform()
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1347, in _do_perform
>     raise err
> urlgrabber.grabber.URLGrabError: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 401"
> :: [   PASS   ] :: Running './grab.py 'http://localhost/grabber/' without.html'
> :: [   FAIL   ] :: File 'output' should contain 'Authorization Required' 
> 
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :: [   LOG    ] :: http with valid user, non-existent file
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> 
> Traceback (most recent call last):
>   File "./grab.py", line 9, in <module>
>     urlgrab(url, filename)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 618, in urlgrab
>     return default_grabber.urlgrab(url, filename, **kwargs)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 985, in urlgrab
>     return self._retry(opts, retryfunc, url, filename)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 886, in _retry
>     r = apply(func, (opts,) + args, {})
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 971, in retryfunc
>     fo = PyCurlFileObject(url, filename, opts)
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1066, in __init__
>     self._do_open()
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1360, in _do_open
>     self._do_grab()
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1490, in _do_grab
>     self._do_perform()
>   File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1347, in _do_perform
>     raise err
> urlgrabber.grabber.URLGrabError: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
> :: [   PASS   ] :: Running './grab.py 'http://httptester:httppassword@localhost/grabber/missing.html' missing.html'
> :: [   FAIL   ] :: File 'output' should contain 'Not Found'
Comment 8 Petr Šplíchal 2011-08-17 08:01:39 UTC 
(In reply to comment #7)
> Does not seem to be fixed. What I get is still just an error
> number. I've tested python-urlgrabber-3.9.1-8.el6.noarch with the
> following results:

For reference curl/pycurl version was:
python-pycurl-7.19.0-8.el6.x86_64
curl-7.19.7-26.el6_1.1.x86_64
Comment 9 James Antill 2011-08-17 19:50:32 UTC 
 Ok, I see what you are saying now. You aren't complaining about no message, but about the fact the message isn't as nice. But that's out of ours hands.

 In RHEL-5 we get the error message from httplib/urllib2 ... which maps "404" into "Not found" etc.
 In RHEL-6 we get the error message from curl/pycurl ... which just says "server responded 404".

 I have no problem with asking curl/pycurl to give better messages ... but I really don't want to parse the error message in urlgrabber and then rewrite it to be better.
Comment 11 Petr Šplíchal 2011-08-18 06:18:15 UTC 
I see, thanks for clarifying. Moving to python-pycurl (see comment #9).
Comment 14 Suzanne Logcher 2012-02-14 23:06:41 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 16 Jan Synacek 2012-07-18 12:30:19 UTC 
(In reply to comment #11)
> I see, thanks for clarifying. Moving to python-pycurl (see comment #9).

I don't think this is a problem of python-pycurl. The patch from https://bugzilla.redhat.com/show_bug.cgi?id=565654 is already there in 6.3.

And if this is not a bug of urlgrabber, there must be something wrong with curl.

The python-pycurl in RHEL 6.3 and Fedora 17 have the same vanilla source. Fedora doesn't even have the patch mentioned in bug #565654.

$ urlgrabber http://www.redhat.com/g

Fedora 17:
[Errno 14] HTTP Error 403 - Forbidden : http://www.redhat.com/g/

RHEL 6.3:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 403"
Comment 17 Jan Synacek 2012-07-18 12:34:25 UTC 
Actually, is this even a bug? It only looks like a different message that is mapped to the specific error code.
Comment 18 Kamil Dudka 2012-07-18 12:53:07 UTC 
> Fedora 17:
> [Errno 14] HTTP Error 403 - Forbidden : http://www.redhat.com/g/
> 
> RHEL 6.3:
> [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 403"

I am not aware of any change in libcurl that would cause the difference above.

(In reply to comment #17)
> Actually, is this even a bug?

I would not say so.  See RFC 2616, 6.1.1:

    "... The client is not required to examine or display the Reason-Phrase."
Comment 19 Kamil Dudka 2012-07-18 21:57:06 UTC 
Error messages are not meant to be stable among releases.  Wherever compatibility matters, HTTP status codes should be used instead of the error messages.  This is apparently not a regression in curl.  I am marking the bug as future feature.
Comment 20 Kamil Dudka 2012-07-20 12:10:37 UTC 
proposed upstream:

http://thread.gmane.org/gmane.comp.web.curl.library/36393
Comment 21 Kamil Dudka 2012-07-22 18:24:31 UTC 
upstream commit:

https://github.com/bagder/curl/commit/d317ca5
Comment 22 Kamil Dudka 2012-07-23 07:44:17 UTC 
fixed in curl-7.26.0-6.fc18
Comment 33 errata-xmlrpc 2013-02-21 10:09:04 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.

http://rhn.redhat.com/errata/RHBA-2013-0393.html
Note You need to log in before you can comment on or make changes to this bug.