[ 
https://issues.apache.org/jira/browse/SLING-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149086#comment-14149086
 ] 

Antonio Sanso commented on SLING-3975:
--------------------------------------

[~cziegeler] this is indeed the problem :) sorry if i wasn't clear enoufh 

This is what happen:

- the request goes through Felix via http://domain.80/active.html but with the 
X-Forwarded-SSL header.
- due FELIX-4420 and s is appended to the schema so the request becomes 
https://domain.80/active.html
 
eventually this leads to inconsistency to the Sling mappings and resource 
resolutions :S

> wrong ResourceResolverImpl#getMapPath value due Apache Felix HTTP SSLFilter
> ---------------------------------------------------------------------------
>
>                 Key: SLING-3975
>                 URL: https://issues.apache.org/jira/browse/SLING-3975
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>            Reporter: Antonio Sanso
>
> The ResourceResolverImpl#getMapPath  method it is a simple method that looks 
> like 
> {code}
>     private static String getMapPath(final String scheme, final String host, 
> int port, final String path) {
>         if (port < 0) {
>             port = ("https".equals(scheme)) ? 443 : 80;
>         }
>         return scheme + "/" + host + "." + port + path;
>     }
> {code}
> The problem is that due the Apache Felix HTTP SSLFilter (FELIX-4420) this 
> method can produce weird value like 
> https/domain.80/active.html !!
> IMHO this method should be somehow aware that the schema was somehow modified 
> in order to avoid producing inconsistent maps.
> [~fmeschbe] WDYT?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to