I get these also. It would be nice if they were logged as a WARN so it
would be easy to ignore them in production.
On Wed, Feb 26, 2014 at 9:19 AM, Lance Java wrote:
> Some serverside actions (eg autocomplete) expect a well formed request
> which may require some request parameters to be present
Some serverside actions (eg autocomplete) expect a well formed request
which may require some request parameters to be present. As you can
imagine, a bot can run regular expressions and hit anything the looks like
a URL. I think it's fine to ignore crawlers from error logging. It's
difficult to do
Thanks for the reply lance.
What does the actual exception mean? Does is it mean a request is being set
with a missing parameter to the autocomplete component? I vaguely remember
seeing this a long time ago while writing a custom autocomplete component.
As far as the logs, I'm hosting the app on
Sounds like a webcrawler / bot to me. Do you have the apache logs? You
could check the user agent header.
As a fix, Google for the list of known bots and their user agent headers
and customised tapestry's exception reporting so that exceptions are not
logged for crawler user agents.
