Reverse mappings may fail for requests with standard ports
----------------------------------------------------------
Key: SLING-785
URL: https://issues.apache.org/jira/browse/SLING-785
Project: Sling
Issue Type: Bug
Components: JCR Resource
Affects Versions: JCR Resource 2.0.4
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: JCR Resource 2.0.4
When creating reverse mappings URLs may be created which contain port numbers
or not, depending on the initial mapping configuration. This is particulary
problematic in cases, where the default port (80 for http and 443 for https) is
used, which may be set in requests or not.
In the incoming URI resolution, this issue is solved by always using the set
port, if the URI does not set it a default is assumed as per the scheme.
The same logic may be applied for reverse mapping, which then would generate
valid URLs, yet they would all include the default port, which is not nice.
Better would be to not use default port specification in outgoing requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
