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)" <de...@tapestry.apache.org> on 2008/09/13 01:21:46 UTC
[jira] Updated: (TAPESTRY-2667) Add configuration to turn off
@Secure when in development
[ https://issues.apache.org/jira/browse/TAPESTRY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2667:
-------------------------------------------
Fix Version/s: 5.1
Summary: Add configuration to turn off @Secure when in development (was: Conditionally set security for pages at startup instead of using the @Secure annotation )
Just clarifying what we talked about ... the idea is to "ignore" HTTPs security if desired, which speeds up development a bit.
> Add configuration to turn off @Secure when in development
> ---------------------------------------------------------
>
> Key: TAPESTRY-2667
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2667
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.14
> Environment: Windows XP
> Reporter: Joey Solis
> Fix For: 5.1
>
>
> In production I want my pages to be secured so I annotate my them with @Secure.
> In development however, I don't want my pages to have to be secured (https) so I comment out the @Secure annotation.
> It would be nice to be able to set the @Secure dynamically based on the environment (development or production).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org