[jira] Updated: (TAPESTRY-991) Switching between HTTPS and HTTP schema, defining which pages are served in which schema

["Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>]

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

Jesse Kuhnert updated TAPESTRY-991:
-----------------------------------

    Fix Version/s:     (was: 4.1.2)
                   4.2

> Switching between HTTPS and HTTP schema, defining which pages are served in which schema
> ----------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-991
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-991
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: Framework
>    Affects Versions: 4.0
>         Environment: Solaris x86 SXCE build 41
>            Reporter: Josip Gracin
>             Fix For: 4.2
>
>
> The problem is that I need to redirect to HTTPS for login and some other subset of pages, and then after login, redirect back to HTTP.  This generalizes to the need for an easy way to specify the schema for each page. 
> As Kevin Menard nicely put it on the mailing list (message id: <op...@kepler.kmkelly.local>):
> "What we (or at least I) want is to deal with this at the page class level.  The idea would be a page class can either be marked as secure or not and the framework would then take care of rewriting URLs with the appropriate scheme.  Such a system would allow for a nice hierarchy of secure pages and likewise would cut down on the human error element by letting the framework do most of the grunt work."

-- 
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