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 2012/05/12 01:41:50 UTC
[jira] [Created] (SLING-2475) Don't create reverse mappings for
regular expression matches
Felix Meschberger created SLING-2475:
----------------------------------------
Summary: Don't create reverse mappings for regular expression matches
Key: SLING-2475
URL: https://issues.apache.org/jira/browse/SLING-2475
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR Resource 2.0.10
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: JCR Resource 2.1.0
Consider the following setup in /etc/map:
any_example_com (sling:Mapping)
.+\.example.com.8080 (sling:match)
/content/example (sling:internalRedirect)
This creates a resolver map entry "^http/(.+)\.example.com.4503 ==> /content/example" which is correct and a mapping map entry "/content/example ==> http://.+\.example.com:8080" which is not correct.
We should in fact try to find out whether an URL to be resolved to an internal one is a regular expression and not create a mapping map entry in these cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2475) Don't create reverse mappings for
regular expression matches
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-2475.
--------------------------------------
Resolution: Fixed
Fixed in Rev. 1337417
> Don't create reverse mappings for regular expression matches
> ------------------------------------------------------------
>
> Key: SLING-2475
> URL: https://issues.apache.org/jira/browse/SLING-2475
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.10
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0
>
>
> Consider the following setup in /etc/map:
> any_example_com (sling:Mapping)
> .+\.example.com.8080 (sling:match)
> /content/example (sling:internalRedirect)
> This creates a resolver map entry "^http/(.+)\.example.com.4503 ==> /content/example" which is correct and a mapping map entry "/content/example ==> http://.+\.example.com:8080" which is not correct.
> We should in fact try to find out whether an URL to be resolved to an internal one is a regular expression and not create a mapping map entry in these cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SLING-2475) Don't create reverse mappings for
regular expression matches
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-2475.
-----------------------------------
> Don't create reverse mappings for regular expression matches
> ------------------------------------------------------------
>
> Key: SLING-2475
> URL: https://issues.apache.org/jira/browse/SLING-2475
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.10
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0
>
>
> Consider the following setup in /etc/map:
> any_example_com (sling:Mapping)
> .+\.example.com.8080 (sling:match)
> /content/example (sling:internalRedirect)
> This creates a resolver map entry "^http/(.+)\.example.com.4503 ==> /content/example" which is correct and a mapping map entry "/content/example ==> http://.+\.example.com:8080" which is not correct.
> We should in fact try to find out whether an URL to be resolved to an internal one is a regular expression and not create a mapping map entry in these cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira