Heya,
we're trying to catch all errors caused by hack & search-bots on our
wicket-app. AFAIK these bots take existing links, chop 'em up in
smaller chunks and try to append all kind of ****. We've caught most
of the errors which result due to these bots, but this one still
stands:
XXX.XXX.XXX.XXX - - [22/Dec/2008:00:03:37 +0100] "GET
/resources/org.apache.wicket.markup.html.WicketEventReference_false_61497/
HTTP/1.1" 404 952 "-" "-" "-"
Causing errors such as
2008-12-22 00:03:41,654 ERROR -
[TP-Processor7][org.apache.wicket.request.target.resource.SharedResourceRequestTarget:172]
unable to lazily register shared resource
org.apache.wicket.ajax.WicketAjaxReference_false_61497/
java.lang.ClassNotFoundException:
org.apache.wicket.ajax.WicketAjaxReference_false_61497
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387)
[...snip...]
So... any ideas to catch these errors?
Antoine
--
We don't see things as they are, we see things as we are. - Anais Nin
Whether you think you can or whether you think you can't, you're
right. - Henry Ford
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
