You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/14 23:28:09 UTC

[jira] [Assigned] (TAP5-1651) It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact

     [ https://issues.apache.org/jira/browse/TAP5-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-1651:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1651
>                 URL: https://issues.apache.org/jira/browse/TAP5-1651
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
> This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira