[ https://issues.apache.org/jira/browse/SLING-5671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-5671: ----------------------------------- Description: The following resource structure: {code} /etc/map + http + localhost:80 + mappedpath - sling:internalRedirect="/content/some/path" {code} leads to the following entry being listed in the outwards (mapping) map (inside {{/system/console/jcrresolver}}) {code} ^/content/some/path/ http://localhost/mappedpath/ external: 302 {code} There are three things wrong here: # the entry in the system console exposes this entry as external redirect with 302 status (although all mapping map entries can only be internal ones IMHO) # That entry incorrectly applies to links towards that path even if the request was done on another port. # Even worse, if the request was done through another port, it will lead to URLs like {{http://localhost/mappedpath/....}} being generated with {{ResourceResolver.map(...)}}. was: The following resource structure: {code} /etc/map + http + localhost:80 + mappedpath - sling:internalRedirect="/content/some/path" {code} leads to the following entry being listed in the outwards (mapping) map (inside {{/system/console/jcrresolver}}) {code} ^/content/some/path/ http://localhost/mappedpath/ external: 302 {code} There are three things wrong here: # the entry in the system console links that as external redirect with 302 (although all mapping map entries can only be internal ones IMHO) # That entry incorrectly applies to links towards that path even if the request was done on another port. # Even worse, if the request was done through another port, it will lead to URLs like {{http://localhost/mappedpath/....}} being generated with {{ResourceResolver.map(...)}}. > Not matching port in the mapping entry still uses the mapping for the outward > mapping (used in ResourceResolver.map) > -------------------------------------------------------------------------------------------------------------------- > > Key: SLING-5671 > URL: https://issues.apache.org/jira/browse/SLING-5671 > Project: Sling > Issue Type: Bug > Components: ResourceResolver > Affects Versions: Resource Resolver 1.4.10 > Reporter: Konrad Windszus > > The following resource structure: > {code} > /etc/map > + http > + localhost:80 > + mappedpath > - sling:internalRedirect="/content/some/path" > {code} > leads to the following entry being listed in the outwards (mapping) map > (inside {{/system/console/jcrresolver}}) > {code} > ^/content/some/path/ http://localhost/mappedpath/ external: 302 > {code} > There are three things wrong here: > # the entry in the system console exposes this entry as external redirect > with 302 status (although all mapping map entries can only be internal ones > IMHO) > # That entry incorrectly applies to links towards that path even if the > request was done on another port. > # Even worse, if the request was done through another port, it will lead to > URLs like {{http://localhost/mappedpath/....}} being generated with > {{ResourceResolver.map(...)}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)