[
https://issues.apache.org/jira/browse/WICKET-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-831.
------------------------------------
Resolution: Fixed
Fix Version/s: 6.15.0
7.0.0
Assignee: Martin Grigorov
In Wicket 6.x there was only one place where an IRequestMapper was throwing an
exception that would lead to error 500.
Now in DEPLOYMENT mode it will be
AbortWithHttpErrorCodeException(HttpServletResponse.SC_NOT_FOUND, message)
> Return response status 404 when a mapper cannot decode a request url
> --------------------------------------------------------------------
>
> Key: WICKET-831
> URL: https://issues.apache.org/jira/browse/WICKET-831
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Jonathan Locke
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 7.0.0, 6.15.0
>
>
> in a real production environment, you will get crawlers and users poking at
> urls and when that happens to produce an invalid request it's probably better
> to 404 the request than throw the current IllegalStateException we throw. we
> might want to step back and think in general about invalid requests in
> production versus development mode. i also think i suggested fairly recently
> that we should add an exception that 404s a request. these two things could
> work together.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
