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 2007/11/19 16:39:43 UTC

[jira] Created: (TAPESTRY-1919) Let Tapestry control HTTP/HTTPS in links via page configuration

Let Tapestry control HTTP/HTTPS in links via page configuration
---------------------------------------------------------------

                 Key: TAPESTRY-1919
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1919
             Project: Tapestry
          Issue Type: New Feature
          Components: tapestry-core
    Affects Versions: 5.0.6
            Reporter: Howard M. Lewis Ship


In general, some pages in an application should be https access only, the rest are good for http.

Tapestry should manage this automatically, using configuration, or an annotation, on pages to indicate they need to be protected via https.

A rare case is a form, usually a login form, that is duplicated throughout the application on otherwise non-protected pages.  The Form component needs a parameter to force the submit request to be HTTPS.

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


[jira] Closed: (TAPESTRY-1919) Let Tapestry control HTTP/HTTPS in links via page configuration

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAPESTRY-1919.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.11

> Let Tapestry control HTTP/HTTPS in links via page configuration
> ---------------------------------------------------------------
>
>                 Key: TAPESTRY-1919
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1919
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.6
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.0.11
>
>
> In general, some pages in an application should be https access only, the rest are good for http.
> Tapestry should manage this automatically, using configuration, or an annotation, on pages to indicate they need to be protected via https.
> A rare case is a form, usually a login form, that is duplicated throughout the application on otherwise non-protected pages.  The Form component needs a parameter to force the submit request to be HTTPS.

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


[jira] Assigned: (TAPESTRY-1919) Let Tapestry control HTTP/HTTPS in links via page configuration

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAPESTRY-1919:
----------------------------------------------

    Assignee: Howard M. Lewis Ship

> Let Tapestry control HTTP/HTTPS in links via page configuration
> ---------------------------------------------------------------
>
>                 Key: TAPESTRY-1919
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1919
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.6
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> In general, some pages in an application should be https access only, the rest are good for http.
> Tapestry should manage this automatically, using configuration, or an annotation, on pages to indicate they need to be protected via https.
> A rare case is a form, usually a login form, that is duplicated throughout the application on otherwise non-protected pages.  The Form component needs a parameter to force the submit request to be HTTPS.

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