From owner-freebsd-questions@FreeBSD.ORG Tue Jul 17 15:53:40 2012 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25AF61065672; Tue, 17 Jul 2012 15:53:40 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from kuller.raad.tartu.ee (kuller.raad.tartu.ee [213.184.43.8]) by mx1.freebsd.org (Postfix) with ESMTP id C1E148FC0A; Tue, 17 Jul 2012 15:53:39 +0000 (UTC) Received: from kuller.raad.tartu.ee (localhost [127.0.0.1]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 681D93984C; Tue, 17 Jul 2012 18:53:38 +0300 (EEST) X-Virus-Scanned: amavisd-new at post.raad.tartu.ee Received: from kuller.raad.tartu.ee ([127.0.0.1]) by kuller.raad.tartu.ee (kuller.raad.tartu.ee [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mZLthYkPRuU1; Tue, 17 Jul 2012 18:53:37 +0300 (EEST) Received: by kuller.raad.tartu.ee (Postfix, from userid 80) id 092D639832; Tue, 17 Jul 2012 18:53:37 +0300 (EEST) Received: from 96.67.235.80.dyn.estpak.ee (96.67.235.80.dyn.estpak.ee [80.235.67.96]) by webmail.raad.tartu.ee (Horde Framework) with HTTP; Tue, 17 Jul 2012 18:53:36 +0300 Message-ID: <20120717185336.202575de6h1c178c@webmail.raad.tartu.ee> Date: Tue, 17 Jul 2012 18:53:36 +0300 From: Toomas Aas To: glarkin@FreeBSD.org References: <20120717145613.20783z1jrv0xapyc@webmail.raad.tartu.ee> <50056D2C.7050508@FreeBSD.org> In-Reply-To: <50056D2C.7050508@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) X-Originating-IP: 80.235.67.96 Cc: questions@freebsd.org Subject: Re: "Twitter.com is loading slowly" after updating to Firefox 13.0.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 15:53:40 -0000 Hello Greg! > I ran into this problem with FF13 on OS X over the weekend, and I > fixed it with a suggestion I found somewhere online: > > Open the about:config preference pane in FF. Change the > http.keep-alive property to "true", and you should be all set. Thanks for the suggestion. I actually saw this recommendation while searching for solution, but in my case network.http.keep-alive was already set to true. Another suggestion was to set 'network.http.spdy.enabled' to 'false', which I did, but this also didn't help. -- Toomas Aas