You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/09/28 22:01:33 UTC
[jira] Commented: (TAP5-1285) Allow GET method in form component
[ https://issues.apache.org/jira/browse/TAP5-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915896#action_12915896 ]
Howard M. Lewis Ship commented on TAP5-1285:
--------------------------------------------
I would be more sympathetic to the POST/GET dichotomy if HTML supported post for hyperlinks, but regardless.
The main issue here is that Tapestry generates a fairly large block of encoded data, the t:formdata hidden field. That will often get truncated in a GET request due to URL length limitations.
> Allow GET method in form component
> ----------------------------------
>
> Key: TAP5-1285
> URL: https://issues.apache.org/jira/browse/TAP5-1285
> Project: Tapestry 5
> Issue Type: Wish
> Components: tapestry-core
> Reporter: Lutz Hühnken
> Priority: Minor
>
> The Tapestry form component is currently only supporting the "POST" method.
> The POST method is usually associated with changing the "model" on the server side, e.g. in REST applications, POST indicates that a resource is modified, if I am not mistaken.
> The lack of GET support makes it necessary to use POST also for simple queries, such as a search field, where the model is not modified.
> This is a) semantically irritating, since for example a search query will not modify state and
> b) requires extra "work", for example a redirect-after-post, where it should not be necessary.
> Since Tapestry aspires to make the simple things easy, the difficult things possible, I think it should provide first-class support for the GET method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.