shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SHIRO-190) PortFilter not accepting custom port
Date Fri, 10 Sep 2010 00:06:36 GMT

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

Les Hazlewood resolved SHIRO-190.
---------------------------------

    Fix Version/s: 1.1.0
       Resolution: Fixed

Committed fix for this and also added an accompanying test case

> PortFilter not accepting custom port
> ------------------------------------
>
>                 Key: SHIRO-190
>                 URL: https://issues.apache.org/jira/browse/SHIRO-190
>             Project: Shiro
>          Issue Type: Bug
>          Components: Web
>    Affects Versions: 1.0.0, 1.0.1, 1.1.0, Incubation
>         Environment: JDK 1.6, OSX 10.5
>            Reporter: Janne Jalkanen
>             Fix For: 1.1.0
>
>
> The following shiro.ini code no worky. Tomcat running on port 8080, with SSL running
on 8443.
> {code}
> [main]
> ssl.port = 8443
> [urls]
> /admin/** = ssl
> {code}
> Access to http://host:8080/admin/foo redirects to https://host:8080/admin/foo, not https://host:8443/admin/foo.
> (It looks to me like PortFilter.onAccessDenied() appends the request.getServerPort()
instead of the port. If I now read this correctly [might not, this is my first foray into
Shiro source], it appears that you can only have SSL on 443 or 80, or else it must be on the
same port as the request itself (?))
> As far as I can tell, this occurs in all versions up until the current trunk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message