You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2007/04/16 04:25:15 UTC
[jira] Closed: (WICKET-411) backport
ISecuritySettings#EnforceMounts functionality
[ https://issues.apache.org/jira/browse/WICKET-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eelco Hillenius closed WICKET-411.
----------------------------------
> backport ISecuritySettings#EnforceMounts functionality
> ------------------------------------------------------
>
> Key: WICKET-411
> URL: https://issues.apache.org/jira/browse/WICKET-411
> Project: Wicket
> Issue Type: Task
> Components: wicket
> Reporter: Eelco Hillenius
> Assigned To: Eelco Hillenius
> Fix For: 1.3
>
>
> A nice feature that is currently only in 2.0 is the ability to 'enforce mounts'. In 2.0 this is regulated through setting ISecuritySettings#EnforeMounts. The JavaDocs:
> /**
> * Gets whether mounts should be enforced. If true, requests for mounted
> * targets have to done through the mounted paths. If, for instance, a
> * bookmarkable page is mounted to a path, a request to that same page via
> * the bookmarkablePage parameter will be denied.
> *
> * @return Whether mounts should be enforced
> */
> This feature was built in to support URL based authorization schemas, and is talked about in Wicket in Action. We should back port it.
> See also WICKET-410
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.