You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jonathan Locke (JIRA)" <ji...@apache.org> on 2008/04/20 21:02:23 UTC

[jira] Commented: (WICKET-831) add a setting to make url decoding errors 404 in production mode

    [ https://issues.apache.org/jira/browse/WICKET-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590796#action_12590796 ] 

Jonathan Locke commented on WICKET-831:
---------------------------------------


yay!

thank you!





> add a setting to make url decoding errors 404 in production mode
> ----------------------------------------------------------------
>
>                 Key: WICKET-831
>                 URL: https://issues.apache.org/jira/browse/WICKET-831
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket
>            Reporter: Jonathan Locke
>            Priority: Minor
>             Fix For: 1.4-M2
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.