You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2011/01/20 14:34:44 UTC

[jira] Commented: (SLING-1938) Mapping might not consider current scheme

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

Felix Meschberger commented on SLING-1938:
------------------------------------------

Further clarification: Consider a setup where a resource, say /content/sample, may be handled by an https or an http request. Wenn mapping such a resource path to an URL, the scheme matching the scheme of the request supplied to the map() method should be preferred.

Example:

     /content/sample ==> http://some.host/content/sample
     /content/sample ==> https://some.host/content/sample

When handling the request "https://a.host/content/start.html" the resource "/content/sample.html" should be mapped to "https://some.host/content/sample.html" while for a request "http://insecure.host/content/start.html" the resource "/content/sample.html" should be mapped to "http://some.host/content/sample.html".

> Mapping might not consider current scheme
> -----------------------------------------
>
>                 Key: SLING-1938
>                 URL: https://issues.apache.org/jira/browse/SLING-1938
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.6
>            Reporter: Carsten Ziegeler
>            Assignee: Felix Meschberger
>             Fix For: JCR Resource 2.0.8
>
>
> If there is a mapping for difference schemes (like on for http and one for https), currently always the first one is picked up. It would make more sense to pick up the mapping with the same scheme as the current request.

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