778338 - FireFox not issuing https request to the server side

Status: RESOLVED INCOMPLETE

(Core :: Networking: HTTP, defect)

Description

[Lee]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11

Steps to reproduce:

Connecting to www.facebook.com and Facebook chat showed in the disconnection state. From firebug plugin, the https request to the Facebook channel domain timed out.  So enter the Facebook channel domain https://0-137.channel.facebook.com in the FF address bar directly and we got a timed out error. 


Actual results:

The request to https://0-137.channel.facebook.com timed out, while the same request url worked on other browsers and with http protocols on FF.  When taking a tcpdump for the request, tcpdump showed no TCP connections from FF to the server. Deleting browser cookies, browser cache or clearing the browser DNS cache did not help with recovery. Starting a new FF browser window did not help either. Disconnecting and reconnecting networks was able to get FireFox back to connect to https://0-137.channel.facebook.com.


Expected results:

The request to https://0-137.channel.facebook.com should work and FF should be sending the request to server side.

Comment 1

[Lee]

We started to get reports of this issue from the past weekend, which seems to be inline with the recent Firefox release. And so far, all the reports are from Mac OS.

Comment 2

[Matthias Versen [:Matti]]

Does it work if you change network.http.spdy.enabled in about:config from true to false ?

A http log could help if you can reproduce this: https://developer.mozilla.org/en/HTTP_Logging

Comment 3

[Patrick McManus [:mcmanus]]

that server isn't running spdy now and I'm not aware of any FF production uses yet. (though we expect them to be coming).

Comment 4

[Patrick McManus [:mcmanus]]

(In reply to Patrick McManus [:mcmanus] from comment #3)
> that server isn't running spdy now and I'm not aware of any FF production
> uses yet. (though we expect them to be coming).

s/FF/FB

Comment 5

[Lee]

Thanks for the replies. I contacted the folks who had the repro early today to collect the HTTP logs. Will update the bug when I get back from them. Thanks.

Comment 6

[Lee]

One possible repro step I got back: 

"I think I found a way to reproduce, by opening and closing the VPN connection using Network Connect. Basically:

1. Have Firefox load https://0-137.channel.facebook.com/p
2. Connect to VPN.
3. Have Firefox load https://0-137.channel.facebook.com/p
4. Disconnect from VPN.
5. Repeat until connecting to the channel server doesn't work.
"

He hasn't collected any usable HTTP logs though. He will try this again during the weekend.

Comment 7

[Lee]

Bob helped collect this log.  This is from Bob: 

Here are the last 1M lines of the Firefox logfile with the chat disconnect issue.

There is a lot of non-Facebook stuff in there as well. I'll try to get a repro without that, but given that it took several days to get this one, I figured I'd just send it to you as-is. Also, these are only the last 1M lines. The original file is about 19GB. I still have it, in case Mozilla need more context.

Link to the log file: https://docs.google.com/open?id=0B4kkufHN7--eVVRpLUhDS0JJY1k

Comment 8

[Lee]

Ping?  Any updates on this bug?  Thanks.

Comment 9

[Patrick McManus [:mcmanus]]

can you check your STR against an aurora build and a beta build?

if it repros on beta but not on aurora it is probly a dup somehow of 762162

Comment 10

[:Gavin Sharp [email: [e-mail]]]

Isn't bug 762162 fixed on both aurora and beta?

Comment 11

[Patrick McManus [:mcmanus]]

(In reply to :Gavin Sharp (use [e-mail] for email) from comment #10)
> Isn't bug 762162 fixed on both aurora and beta?

762162 was backed out of beta because it needed followon fixes that were deemed suitable for just aurora... I updated the original bug to reflect that just now:

https://bugzilla.mozilla.org/show_bug.cgi?id=762162#c62

Comment 12

[Lee]

Patrick: I still have one question about the pointed duplicate #762162. Bug #762162 seems to be already existing in FF13 and was reported back in June.  But we only started to get reports of the issues after the July 17 FF14 release.  We will test the new FF build and let you know if we still see the problem. Thanks.