from the log at our production tomcat, we find that there are strange requests to wicket resources
we do not meet that at our daily development or daily access to our production site we have suspected if this is "attack", but this may not be as the frequency is low, so is the problem caused by "codes" ? some examples: referrer: http://<my domain>/resources/org.apache.wicket.markup.html.WicketEventReference/+sfgRmluamFuX1R5cGU9amF2YV9zY3JpcHQmRmluamFuX0xhbmc9dGV4dC9qYXZhc2NyaXB0+/(window.location.protocol request path: /resources/resources/org.apache.wicket.markup.html.WicketEventReference/wicket-event.js agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) referrer: http://<my domain>/resources/org.apache.wicket.markup.html.WicketEventReference/+sfgRmluamFuX1R5cGU9amF2YV9zY3JpcHQmRmluamFuX0xhbmc9dGV4dC9qYXZhc2NyaXB0+/wicket-event.js request path: /resources/org.apache.wicket.markup.html.WicketEventReference/(window.location.protocol agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727) -- View this message in context: http://www.nabble.com/strange-resource-references-leading-to-404-tp19966705p19966705.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]