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:
My setup uses OpenSSH's dynamic forwarding feature to set up a SOCKS tunnel from local port 10000 to the destination host. Firefox is set to use this tunnel with its SOCKS proxy. Remote DNS lookup is also enabled.
I discovered this problem while browsing Facebook. Images posted by users were not showing up. Using a combination of Page Info (Media tab) and Wireshark, I determined that to download images, it was attempting to connect to scontent-a.facebook.com and scontent-b.facebook.com using the SOCKS connect command. Neither of these hosts exist. I turned on HTTP logging (NSPR_LOG_MODULES=nsHttp:5 and NSPR_LOG_FILE=http.log) and discovered that the actual host names, scontent-a.xx.fbcdn.net and scontent-b.xx.fbcdn.net, were coalescing with www.facebook.com. This seems to interact badly with the transparent proxy (SOCKS) where it attempts to contact the "coalesced" server names instead of reusing its connections as SPDY intends.
Turning off hostname coalescing in about:config is a workaround.
Version-Release number of selected component (if applicable):
17.0.10
How reproducible:
Always
Steps to Reproduce:
1. Use OpenSSH to connect to another host, and set up a dynamic port forward (-D option in OpenSSH).
2. Set Firefox to use that dynamic port with SOCKS
3. Browse Facebook photos
Actual results:
The page appears, sans photos. Page Info/Media tab shows images that come from scontent-a or scontent-b hosts as 0KB and 0x0 size.
Expected results:
Photos also appear
Additional info:
A snippet of the HTTP log:
1820325632[7fea791537b0]: nsHttpConnectionMgr::GetSpdyPreferredConnection Host www.facebook.com cannot be confirmed to be joined with fbstatic-a.akamaihd.net connections. rv=0 isJoined=0
1820325632[7fea791537b0]: nsHttpConnectionMgr::ProcessPendingQForEntry [ci=.S.fbcdn-photos-f-a.akamaihd.net:443 (socks)]
1820325632[7fea791537b0]: nsHttpConnectionMgr::GetSpdyPreferredConnection Host www.facebook.com cannot be confirmed to be joined with fbcdn-photos-f-a.akamaihd.net connections. rv=0 isJoined=0
1820325632[7fea791537b0]: nsHttpConnectionMgr::ProcessPendingQForEntry [ci=.S.scontent-a.xx.fbcdn.net:443 (socks)]
1820325632[7fea791537b0]: nsHttpConnectionMgr::GetSpdyPreferredConnection Host www.facebook.com has cert valid for scontent-a.xx.fbcdn.net connections, so scontent-a.xx.fbcdn.net will be coalesced with www.facebook.com
1820325632[7fea791537b0]: nsHttpConnectionMgr::ProcessPendingQForEntry [ci=.S.fbcdn-creative-a.akamaihd.net:443 (socks)]
1820325632[7fea791537b0]: nsHttpConnectionMgr::GetSpdyPreferredConnection Host www.facebook.com cannot be confirmed to be joined with fbcdn-creative-a.akamaihd.net connections. rv=0 isJoined=0
1820325632[7fea791537b0]: nsHttpConnectionMgr::ProcessPendingQForEntry [ci=.S.fbcdn-photos-d-a.akamaihd.net:443 (socks)]
1820325632[7fea791537b0]: nsHttpConnectionMgr::GetSpdyPreferredConnection Host www.facebook.com cannot be confirmed to be joined with fbcdn-photos-d-a.akamaihd.net connections. rv=0 isJoined=0
...
1820325632[7fea791537b0]: nsHttpConnectionMgr::ProcessPendingQForEntry [ci=.S.scontent-a.facebook.com:443 (socks)]
That sounds good. If you find corresponding bug at https://bugzilla.mozilla.org/ we can consider to include the patch in some next update. Otherwise it will be bundled in next Firefox ESR rebase, when the 24 line comes EOL.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/