You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/13 15:23:29 UTC

[jira] [Closed] (TAP5-730) Add setSecure() to TestableRequest

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

Jochen Kemnade closed TAP5-730.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> Add setSecure() to TestableRequest
> ----------------------------------
>
>                 Key: TAP5-730
>                 URL: https://issues.apache.org/jira/browse/TAP5-730
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Paul Field
>              Labels: bulk-close-candidate
>
> Please could you add:
> setSecure(boolean)
> to TestableRequest so it is possible to write tests where the behaviour is different for secure vs insecure requests (for example testing alternative implementations of RequestSecurityManager).



--
This message was sent by Atlassian JIRA
(v6.2#6252)