[ http://issues.apache.org/jira/browse/TAPESTRY-1064?page=all ]
Jesse Kuhnert resolved TAPESTRY-1064.
-------------------------------------
Resolution: Fixed
Sounds like a good idea to me. Will show up in tonights 4.1.1 SNAPSHOT build.
> Add isSecure to WebRequest interface
> ------------------------------------
>
> Key: TAPESTRY-1064
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1064
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Reporter: Jeff Lubetkin
> Fix For: 4.1.1
>
>
> In trying to build SSL support into my Tapestry application, I find that I'm
> occasionally having to jump through hoops to get to
> HttpServletRequest.isSecure in places where I have easy access to a
> WebRequest. In some cases, access to the scheme and port are not enough to
> determine if the request is secure. It'd be great if this method could be
> added to WebRequest directly. From what I can find it's supported in
> PortletRequests as well, so there should be no issue with support in both
> environments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
