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 1439798 - libsoup stuck on infinite loop for kerberized pages
Summary: libsoup stuck on infinite loop for kerberized pages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libsoup
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Popela
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-06 14:34 UTC by Michal Odehnal
Modified: 2017-08-01 19:32 UTC (History)
2 users (show)

Fixed In Version: libsoup-2.56.0-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 19:32:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 783780 0 None None None 2017-06-14 10:07:30 UTC
Red Hat Product Errata RHEA-2017:2146 0 normal SHIPPED_LIVE libsoup bug fix update 2017-08-01 18:17:04 UTC

Description Michal Odehnal 2017-04-06 14:34:14 UTC 
Description of problem:
Unable to load https://tcms.engineering.redhat.com via webkitgtk4 

Version-Release number of selected component (if applicable):
webkitgtk4-2.14.5-5.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start /usr/libexec/webkit2gtk-4.0/MiniBrowser https://tcms.engineering.redhat.com
2.
3.

Actual results:
Nothing is displayed

Expected results:
TCMS page correctly displayed

Additional info:
Comment 2 Michal Odehnal 2017-04-06 14:47:18 UTC 
Console output upon opening:
/usr/libexec/webkit2gtk-4.0/WebKitWebProcess: symbol lookup error: /lib64/libwebkit2gtk-4.0.so.37: undefined symbol: gtk_widget_path_iter_set_object_name
Comment 3 Tomas Popela 2017-04-06 14:53:43 UTC 
(In reply to Michal Odehnal from comment #2)
> Console output upon opening:
> /usr/libexec/webkit2gtk-4.0/WebKitWebProcess: symbol lookup error:
> /lib64/libwebkit2gtk-4.0.so.37: undefined symbol:
> gtk_widget_path_iter_set_object_name

You don't have gtk3 package from 7.4 installed. The error that I see is:

(process:17033): libsoup-WARNING **: SoupMessage 0x5628b94be940 stuck in infinite loop?
Comment 4 Michal Odehnal 2017-04-06 15:00:15 UTC 
Console output upon opening in VM:
(process:7189): libsoup-WARNING **: gssapi step failed: Unspecified GSS failure.  Minor code may provide more information: SPNEGO cannot find mechanisms to negotiate
Comment 5 Tomas Popela 2017-04-06 15:15:00 UTC 
Reproducible with get utility from libsoup:

./get -d -N -c ~/Documents/red_hat_ca_cert.crt https://tcms.engineering.redhat.com

I'm moving it to the right component (libsoup) before I will investigate it further.
Comment 6 Tomas Popela 2017-04-07 08:29:07 UTC 
OK, so the tcms is sending the following response to the initial GET:

< HTTP/1.1 401 Authorization Required
< Soup-Debug-Timestamp: 1491552071
< Soup-Debug: SoupMessage 1 (0x2083bd0)
< Date: Fri, 07 Apr 2017 08:01:11 GMT
< Server: Apache/2.2.15 (Red Hat)
< WWW-Authenticate: Negotiate
< WWW-Authenticate: Basic realm="TCMS - Kerberos login (if negotiate unavailable)"
< Last-Modified: Thu, 08 Dec 2016 08:15:51 GMT
< ETag: "9fb30-0-543213ee8e70f"
< Accept-Ranges: bytes
< Vary: Accept-Encoding
< Content-Encoding: gzip
< Content-Length: 20
< Connection: close
< Content-Type: text/plain; charset=UTF-8

The problem here is the request to close the connection. This is causing the connection to be closed and the authentication process to be restarted. For example the errata server specifies the connection to be kept alive, which I think is the right thing to do. But I need to confirm it the the kerberos guys.
Comment 10 errata-xmlrpc 2017-08-01 19:32:29 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://access.redhat.com/errata/RHEA-2017:2146
Note You need to log in before you can comment on or make changes to this bug.