Hi,
On Fri, Mar 14, 2014 at 4:11 PM, jchappelle <jchappe...@4redi.com> wrote: > Hi Martin, > > Thanks for the quick reply. > > We don't currently detect duplicate issues automatically. We do get several > duplicates from users because they tend to click the same bad button over > and over. I'm not too worried about attackers because you have to log in to > get anywhere in our application. The way I have thought about doing it is > having a sourceId in our ErrorReport class that would identify the report. > The sourceId might be the page and breadcrumb trail or something of that > nature. Then the ErrorReportingService would keep maybe keep a hash of the > sourceId or store the sourceId's in the database and make sure others with > that id are not sent for a certain time window. Although that is not > perfect, because it could prevent errors from getting to us that need to. > > Can I make a new feature issue in JIRA for the DefaultExceptionMapper to > pass the exception to the constructor of the internal error page? Maybe it > could be a new type of UnexpectedExceptionDisplay in IExceptionSettings > called SHOW_INTERNAL_ERROR_PAGE_WITH_EXCEPTION. That way it doesn't risk > breaking existing users' internal error pages. > With a patch would be awesome! > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Pass-exception-to-internal-error-page-tp4664951p4664973.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
