[
https://issues.apache.org/jira/browse/TAP5-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-883:
------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> 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
> Labels: bulk-close-candidate
>
> 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 anchored regexps like ^[a-z]{2}$
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
