Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem
======================
Some HTTP responses (HTTP 200 is affected, but there could be others) generated by openwsman-server contain string '(null)' as Reason Phrase, ie. in first line after the status code.
For example, this is a HTTP 200 response after Basic Auth:
HTTP/1.1 200 (null)
Server: openwsman/2.6
...
(The preceding 401 response is not affected, ie. shows '401
Unauthorized'.)
Version-Release number of selected component
============================================
openwsman-server-2.3.6-14.el7
openwsman-client-2.3.6-14.el7
How reproducible
================
Always
Steps to Reproduce
==================
Set up server to Basic Auth and call:
xsd=http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
wsman -d 6 -v -h localhost -P 5985 -u wsman -p wsman get $xsd
Observe the output and look for HTTP 200 response (after HTTP 401 and
authentication).
Actual results
==============
First line is:
HTTP/1.1 200 (null)
Expected results
================
First line should be:
HTTP/1.1 200 OK
Note that acccording to RFC 2616[1], the Reason Phrase is for human reader only.
> The Status-Code element is a 3-digit integer result code of the attempt to
> understand and satisfy the request. These codes are fully defined in section
> 10. The Reason-Phrase is intended to give a short textual description of the
> Status-Code. The Status-Code is intended for use by automata and the
> Reason-Phrase is intended for the human user. The client is not required to
> examine or display the Reason- Phrase.
[1]: https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html
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://access.redhat.com/errata/RHBA-2018:0829
Description of problem ====================== Some HTTP responses (HTTP 200 is affected, but there could be others) generated by openwsman-server contain string '(null)' as Reason Phrase, ie. in first line after the status code. For example, this is a HTTP 200 response after Basic Auth: HTTP/1.1 200 (null) Server: openwsman/2.6 ... (The preceding 401 response is not affected, ie. shows '401 Unauthorized'.) Version-Release number of selected component ============================================ openwsman-server-2.3.6-14.el7 openwsman-client-2.3.6-14.el7 How reproducible ================ Always Steps to Reproduce ================== Set up server to Basic Auth and call: xsd=http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd wsman -d 6 -v -h localhost -P 5985 -u wsman -p wsman get $xsd Observe the output and look for HTTP 200 response (after HTTP 401 and authentication). Actual results ============== First line is: HTTP/1.1 200 (null) Expected results ================ First line should be: HTTP/1.1 200 OK