Closed Bug 724478 Opened 13 years ago Closed 13 years ago

Since the release of firefox 10 our site got very much delay.

Categories

(NSS :: Libraries, defect)

3.13
x86_64
All
defect
Not set
critical

Tracking

(firefox10 wontfix, firefox11 wontfix, firefox12 wontfix, firefox13 wontfix, firefox-esr10- wontfix, status1.9.2 unaffected)

RESOLVED WORKSFORME
Tracking Status
firefox10 --- wontfix
firefox11 --- wontfix
firefox12 --- wontfix
firefox13 --- wontfix
firefox-esr10 - wontfix
status1.9.2 --- unaffected

People

(Reporter: stefan.jansson, Unassigned)

References

()

Details

(Keywords: regression)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20100101 Firefox/10.0 Build ID: 20120129021758 Steps to reproduce: Visiting our website (www.avanza.se) Actual results: The site runs very slow, delays over 1 second. Before firefox 10 was released it had response times under 100ms. With FF10 it is 1+ second. Expected results: The site is running very fast with other versions of firefox and internet explorer.
Severity: normal → critical
The most helpful thing for this issue would be for us to be able to see the network requests that Firefox is making on your machine. You can do this by following these steps https://developer.mozilla.org/en/HTTP_Logging If you have any questions about the steps reply to this bug and I'll do my best to assist you.
Attached file log file when viewing the page. (deleted) —
(In reply to Kevin Brosnan [:kbrosnan] from comment #1) > The most helpful thing for this issue would be for us to be able to see the > network requests that Firefox is making on your machine. You can do this by > following these steps https://developer.mozilla.org/en/HTTP_Logging > > If you have any questions about the steps reply to this bug and I'll do my > best to assist you. I have attached the log file now.
I think I have solved this. It seems to be record splitting that cause this problem. By using rsa-rc4-128-sha the delay goes away.
WFM: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.26) Gecko/20120128 Firefox/3.6.26 Reproduced: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20100101 Firefox/10.0 Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Mozilla/5.0 (X11; Linux x86_64; rv:12.0a2) Gecko/20120206 Firefox/12.0a2 Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/20120206 Firefox/13.0a1 Last good nightly: 2011-10-07 First bad nightly: 2011-10-08 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c3a50afc2243&tochange=6c780dcb4b99
Keywords: regression
OS: Windows 7 → All
Version: 10 Branch → Trunk
The first bad revision is: changeset: 78350:8f011395145e user: Brian Smith <bsmith@mozilla.com> date: Fri Oct 07 13:37:26 2011 -0700 summary: Bug 669061: Upgrade to NSS 3.13 RC0, r=wtc https://hg.mozilla.org/mozilla-central/rev/8f011395145e
Blocks: 669061
Assignee: nobody → nobody
Status: UNCONFIRMED → NEW
Component: Untriaged → Libraries
Ever confirmed: true
Product: Firefox → NSS
QA Contact: untriaged → libraries
Version: Trunk → 3.13
This problem was not caused by firefox itself. The problem is with Cisco SSL accelerator (WS-SVC-SSL-1) It is fixed by forcing clients using RC4 based ciphers.
Resolution of this issue appears to be outside the Firefox product. No need to track for ESR10.
This was due to our fix for the "BEAST" attack, and eventually all browsers will behave this way.
Considering comment 9, should the current bug be resolved as INVALID?
Status: NEW → RESOLVED
Closed: 13 years ago
Depends on: 702111
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: