tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2436) Don't throw an IllgealArgumentException on illegal chars in the url
Date Wed, 12 Aug 2015 10:30:46 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693296#comment-14693296
] 

Hudson commented on TAP5-2436:
------------------------------

ABORTED: Integrated in tapestry-trunk-freestyle #1477 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1477/])
TAP5-2436: if the activation context contains illegal characters, respond with a HTTP 404
status (jochen.kemnade: rev a05f9618630db905feeb307ead6dcef2e6a5c3bc)
* tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ComponentEventLinkEncoderImpl.java
* tapestry-core/src/test/java/org/apache/tapestry5/internal/services/ComponentEventLinkEncoderImplTest.java


> Don't throw an IllgealArgumentException on illegal chars in the url
> -------------------------------------------------------------------
>
>                 Key: TAP5-2436
>                 URL: https://issues.apache.org/jira/browse/TAP5-2436
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: quurks
>            Assignee: Jochen Kemnade
>              Labels: patch
>             Fix For: 5.4
>
>         Attachments: 0001-TAP5-2436-if-the-activation-context-contains-illegal.patch
>
>
> A few days ago some tool tried to find vulnerabilites by checking urls like /pageid=99999'
. This lead to dozens of exception reports like 
> Exception type: java.lang.IllegalArgumentException
> Message: Input string 'pageid=99999'' is not valid; the character '=' at position 7 is
not valid.
> This should either be a custom exception type, so it can be handled without parsing the
IllegalArgumentException message or it should be a 400 - Bad request, which would also allow
for a custom error page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message