tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Lattermann (JIRA)" <j...@apache.org>
Subject [jira] Created: (TAP5-883) Regexp validator behaviour differs on client and server side
Date Thu, 08 Oct 2009 10:46:31 GMT
Regexp validator behaviour differs on client and server side
------------------------------------------------------------

                 Key: TAP5-883
                 URL: https://issues.apache.org/jira/browse/TAP5-883
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.1.0.5
            Reporter: Dirk Lattermann
            Priority: Minor


In some situations, a value can pass client side regexp validation and fail the server side
validation. This should not be the case.

The server regexp validator requires a value to match the regexp exactly from start to end
which is not the case on the client (browser).

For example, given a regexp of [a-z]{2}, a value of hu4 passes validation on the client and
fails on the server.

Workaround: use anchord regexps like ^[a-z]{2}$


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message