[
https://issues.apache.org/jira/browse/SHIRO-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Demers updated SHIRO-360:
-------------------------------
Fix Version/s: (was: 1.3.0)
2.0.0
I think we also need to think bumping Shiro's minimum servlet spec version to 3
to support the getEffectiveSessionTrackingModes() method.
This is a separate issue, but related to sessionId handling
> Create UrlEncoder
> -----------------
>
> Key: SHIRO-360
> URL: https://issues.apache.org/jira/browse/SHIRO-360
> Project: Shiro
> Issue Type: New Feature
> Components: Web
> Reporter: Les Hazlewood
> Fix For: 2.0.0
>
>
> To customize how URL encoding in a web app occurs, we should have a
> UrlEncoder component. More specifically, this can be used to customize how
> JSESSIONID is appended to a URL (if at all, depending on security
> preferences).
> The solution could be resolved as follows:
> Create a new UrlEncoder interface:
> public interface UrlEncoder {
> String encodeUrl(EncodeUrlRequest request);
> }
> The EncodeUrlRequest:
> public interface EncodeUrlRequest {
> String getUrl();
> HttpServletRequest getHttpServletRequest();
> HttpServletResponse getHttpServletResponse();
> ServletContext getServletContext();
> }
> Update WebEnvironment to have a new property:
> UrlEncoder getUrlEncoder();
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
