Details
-
Type: Bug
-
Status: Open
-
Priority: Trivial
-
Resolution: Unresolved
-
Affects Version/s: 4.7.6
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
Description
I'm not quite sure the answer but we had a customer report a server outage from a query that turned out to be as a result of someone accessing the Mailing Detail Report without any criteria. Without criteria this report queries mailing tables which are regularly over 100MB indiscriminately.
As a stop gap I have added to their site a statusBounce to enforce providing an id when accessing the report. I'm not sure what a more nuanced approach would look like