Closed
Bug 726133
Opened 12 years ago
Closed 12 years ago
Firefox Aurora Flash content not displaying on indexes.nasdaqomx.com
Categories
(Firefox :: Untriaged, defect)
Firefox
Untriaged
Tracking
()
RESOLVED
DUPLICATE
of bug 724465
People
(Reporter: codewzrd, Unassigned)
References
()
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0a2) Gecko/20120209 Firefox/12.0a2 Build ID: 20120209042012 Steps to reproduce: I upgraded to Firefox Aurora 12 (12.0a2 (2012-02-09)). Actual results: When I go to https://indexes.nasdaqomx.com, the highlighted index section flash component display's no data. If you go to https://indexes.nasdaqomx.com/data.aspx?IndexSymbol=NDX the chart in the middle of page does not render. Both are flash components. Expected results: All flash components should render. As it does in Firefox Beta and Release, IE 9,8,7, and Chrome 16.
Comment 1•12 years ago
|
||
WFM: 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 Reproduced: Mozilla/5.0 (X11; Linux x86_64; rv:12.0a2) Gecko/20120210 Firefox/12.0a2 Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/20120210 Firefox/13.0a1 Last good nightly: 2012-01-12 First bad nightly: 2012-01-13 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8ffdb4c7404a&tochange=964b118ac852
Comment 2•12 years ago
|
||
The first bad revision is: changeset: 84335:c98283f80ae7 user: Doug Turner <dougt@dougt.org> date: Thu Jan 12 09:59:59 2012 -0800 summary: Bug 704467 - Crash in mozalloc_abort | __swrite | dexDataMapAlloc. Protect against a bad class cast. r=wesj http://hg.mozilla.org/mozilla-central/rev/c98283f80ae7 Hmmm, did something go wrong in the bisecting? Is this a plausible culprit? My wild guess before the bisecting was bug 410904.
Comment 3•12 years ago
|
||
The first bad revision is: changeset: 84303:65da0d7b408d user: Fabien Cellier <fabien.cellier@gmail.com> date: Wed Jan 11 14:38:19 2012 -0500 summary: bug 410904 : add referrer in http request from npapi. r=josh https://hg.mozilla.org/mozilla-central/rev/65da0d7b408d I checked out a new, fresh source tree and landed on bug 410904 this time - like I had guessed from the very beginning.
Comment 4•12 years ago
|
||
Error Message from https://indexes.nasdaqomx.com/data.aspx?IndexSymbol=NDX: Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: 'https://luda.nasdaq.com/weborb/weborb.aspx' pcl --- Some kind of hotlink protection that sends 404 Not Found instead of 403 Forbidden?
Comment 5•12 years ago
|
||
Regression window(m-i) Works: http://hg.mozilla.org/integration/mozilla-inbound/rev/39b93b408124 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120111 Firefox/12.0a1 ID:20120111092924 Fails: http://hg.mozilla.org/integration/mozilla-inbound/rev/5660fa471b73 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120111 Firefox/12.0a1 ID:20120111113924 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=39b93b408124&tochange=5660fa471b73 and network.http.sendRefererHeader = 1 helps
Comment 6•12 years ago
|
||
Firebug shows a couple of 400 Bad Request using Firefox 13, but that does not happen in Firefox 10.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Comment 7•12 years ago
|
||
(In reply to Thomas Ahlblom from comment #6) > Firebug shows a couple of 400 Bad Request using Firefox 13, but that does > not happen in Firefox 10. if set network.http.sendRefererHeader = 1 , no such error appears. This is sure causes of bug 410904.
Updated•12 years ago
|
tracking-firefox12:
--- → ?
tracking-firefox13:
--- → ?
Updated•12 years ago
|
Comment 8•12 years ago
|
||
Please retest with tomorrows nightly. We removed the referer on http post initiated by plugins
Comment 9•12 years ago
|
||
The Server is IIS 6 and this is works with Mozilla/5.0 (Windows NT 6.1; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1 SeaMonkey/2.10a1 marking as dupe of bug 724465
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•12 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•