Plugins.mozilla.org overrun due to users from Flash Blocklist link

RESOLVED WONTFIX

Status

addons.mozilla.org Graveyard
Public Pages
--
blocker
RESOLVED WONTFIX
3 years ago
2 years ago

People

(Reporter: Tomcat, Unassigned)

Tracking

Details

(Reporter)

Description

3 years ago
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

3 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
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

3 years ago
I believe we addressed this issue by beefing up plugins.mozilla.org instead (BZ 1127254).
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
(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

3 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.
(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

3 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

2 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.