You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2010/08/04 14:18:17 UTC

[jira] Reopened: (SLING-1219) Map test in JCR Resource Resolver web console plugin is not reflecting all cases

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

Alexander Klimetschek reopened SLING-1219:
------------------------------------------


Reopening because the check for using the map(String) variant is wrong.

Instead of using "getRemoteHost() == null" (always != null) it must check "getServerName() == null", which is the important part that is set when the user enters an absolute URI in the test field as opposed to just a path.

(Reopening as 2.0.8 isn't released yet)

> Map test in JCR Resource Resolver web console plugin is not reflecting all cases
> --------------------------------------------------------------------------------
>
>                 Key: SLING-1219
>                 URL: https://issues.apache.org/jira/browse/SLING-1219
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.6
>            Reporter: Alexander Klimetschek
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: JCR Resource 2.0.8
>
>         Attachments: SLING-1219.patch
>
>
> The "Map" test in the web console plugin of the JCR resource resolver is actually doing a
>  ResourceResolver.map(request, path)
> with the request being something like "http://null", without even noting that. This is misleading as one would at least expect that the current server is used (ie. how the web console is accessed), eg. http://localhost in most cases. This difference will give different results in many cases, eg. if an internal redirect based on localhost.80 is configured.
> Also, there is a second map() only accepting a path which behaves different in that it will always add the domain prefix if configured.
> For proper testing there should be a way to do all of them.

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