[
https://issues.apache.org/jira/browse/TAP5-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679792#action_12679792
]
Howard M. Lewis Ship commented on TAP5-43:
------------------------------------------
My thought is that there's a configuration symbol, tapestry.enable-secure that
defaults to "true". By adding -Dtapestry.enable-secure=false it can be turned
off for development.
If you want to connect it to production, you can override the symbol's value as
"${tapestry.production-mode}".
> Add configuration to turn off @Secure when in development
> ---------------------------------------------------------
>
> Key: TAP5-43
> URL: https://issues.apache.org/jira/browse/TAP5-43
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Environment: Windows XP
> Reporter: Joey Solis
> Assignee: Howard M. Lewis Ship
>
> 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.
