NS_ABORT_IF_FALSE(mConnectionInfo->UsingSSL()) failing [websockets http proxy]

RESOLVED FIXED in mozilla16

Status

()

Core
Networking: HTTP
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: mayhemer, Assigned: jduell)

Tracking

Trunk
mozilla16
x86_64
Windows 7
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [http-conn])

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Trying to reproduce bug 766817 with http://www.websocket.org/echo.html.  Using squid configured for authentication (standard config).  When clicking the [connect] button, I'm getting assertion failure at http://hg.mozilla.org/mozilla-central/annotate/10e019421e6b/netwerk/protocol/http/nsHttpChannel.cpp#l1002

    NS_ABORT_IF_FALSE(mConnectionInfo->UsingSSL(),
                      "SSL connect failed but not using SSL?");

Http status is 403, host is echo.websocket.org, port 80.  mSSLConnectFailed is set to 'true' on the transaction.

Candidate for bug 715905?
it might be as simple as the ABORT being superfulous. iirc websockets uses connect to make a websockets tunnel through the proxy.. That path is the failed-to-make-tunnel path.. off the top of my head the error handling is going to be the same even in the absence of SSL.. but it obviously needs more rigor than that.
Summary: NS_ABORT_IF_FALSE(mConnectionInfo->UsingSSL()) failing → NS_ABORT_IF_FALSE(mConnectionInfo->UsingSSL()) failing [websockets http proxy]
(Assignee)

Updated

5 years ago
Assignee: nobody → jduell.mcbugs
(Assignee)

Comment 2

5 years ago
Created attachment 635841 [details] [diff] [review]
fix abort.

Patrick's comment is right about the issue.  I grepped through the code to audit all uses of "SSL" and found a few other bugs, and a lot of stuff that should get renamed.  Filing separate bugs for those so we can sort out which deserve aurora/beta, if any.  Not sure if this one does, for instance (doesn't affect release builds).
Attachment #635841 - Flags: review?(mcmanus)
(Assignee)

Updated

5 years ago
Blocks: 767516
(Assignee)

Comment 3

5 years ago
Whoops--since this depends on bug 713026 and that isn't making it to aurora/beta, it's moot to consider backporting this as well.
Depends on: 713026
Comment on attachment 635841 [details] [diff] [review]
fix abort.

Review of attachment 635841 [details] [diff] [review]:
-----------------------------------------------------------------

the assert reason should be updated.. and maybe the general comments for the function too - I wouldn't go too crazy chasing the rabbit down the hole here though.
Attachment #635841 - Flags: review?(mcmanus) → review+
(Assignee)

Comment 5

5 years ago
Comments for the assertion and the function generally got updated in bug 767516. 

https://hg.mozilla.org/integration/mozilla-inbound/rev/4eca26d02c84
Push backed out for M5 orange:
https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=d45ca69b67a3

Couldn't see you on #developers or see any try run URLs listed in-bug in the four bugs in the push, or I would have tried to find out if just part of it could have been backed out.

https://hg.mozilla.org/integration/mozilla-inbound/rev/51cff2123f45
(Reporter)

Comment 7

5 years ago
Jason, could we land just this one single patch?
(Assignee)

Comment 8

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/9b12977096b9
https://hg.mozilla.org/mozilla-central/rev/9b12977096b9
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
You need to log in before you can comment on or make changes to this bug.