Closed
Bug 1127268
Opened 9 years ago
Closed 9 years ago
Plugins.mozilla.org overrun due to users from Flash Blocklist link
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cbook, Unassigned)
Details
seems the text on: Blocked: https://addons.mozilla.org/en-US/firefox/blocked/p828 https://addons.mozilla.org/en-US/firefox/blocked/p826 https://addons.mozilla.org/en-US/firefox/blocked/p824 with "All users are strongly recommended to check for updates on our plugin check page." is now causing a massive spike in users hitting plugincheck and so plugins.mozilla.org (the db) is overrun by requests . Can we change this text on 3 pages away from plugincheck to give the servers and db a chance to recover ?
Comment 1•9 years ago
|
||
It's not just the text on those three pages that's driving people to the plugincheck page. Users are also directed to plugincheck when they click on the red "Check for updates..." button on the blocked plugin content. See https://support.mozilla.org/en-US/kb/why-do-i-have-click-activate-plugins#w_how-click-to-activate-works Related discussion: https://support.mozilla.org/en-US/forums/contributors/711040?#post-63882
Comment 2•9 years ago
|
||
It looks like we caught the load early enough and a bunch of folks on #moc jumped in. At the moment we are all good.
Comment 3•9 years ago
|
||
I believe we addressed this issue by beefing up plugins.mozilla.org instead (BZ 1127254).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Comment 4•9 years ago
|
||
(In reply to Alice Wyman from comment #1) > It's not just the text on those three pages that's driving people to the > plugincheck page. Users are also directed to plugincheck when they click on > the red "Check for updates..." button on the blocked plugin content. See > https://support.mozilla.org/en-US/kb/why-do-i-have-click-activate- > plugins#w_how-click-to-activate-works > Related discussion: > https://support.mozilla.org/en-US/forums/contributors/711040?#post-63882 I wanted to say it will points to https://get.adobe.com/flashplayer/ since Fx 36 as a result of bug 1038145, but it doesn't work as expected, filed as bug 1129287.
Comment 5•9 years ago
|
||
(In reply to Hector Zhao [:hectorz] from comment #4) > (In reply to Alice Wyman from comment #1) > > It's not just the text on those three pages that's driving people to the > > plugincheck page. Users are also directed to plugincheck when they click on > > the red "Check for updates..." button on the blocked plugin content. See > > https://support.mozilla.org/en-US/kb/why-do-i-have-click-activate-plugins#w_how-click-to-activate-works > > <snip> > > I wanted to say it will points to https://get.adobe.com/flashplayer/ since > Fx 36 as a result of bug 1038145, but it doesn't work as expected, filed as > bug 1129287. Thank you. I'll update that article for fx36.
Comment 6•9 years ago
|
||
(In reply to Alice Wyman from comment #5) > > Thank you. I'll update that article for fx36. Sorry but I'm wrong about this, the "Check for updates..." link always points to plugincheck. The plugin info url introduced in bug 1038145 is limited to the CtP ui.
Comment 7•9 years ago
|
||
(In reply to Hector Zhao [:hectorz] from comment #6) > (In reply to Alice Wyman from comment #5) > > > > Thank you. I'll update that article for fx36. > > Sorry but I'm wrong about this, the "Check for updates..." link always > points to plugincheck. The plugin info url introduced in bug 1038145 is > limited to the CtP ui. Thanks again.
Assignee | ||
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•