[SLING-785] Reverse mappings may fail for requests with standard ports

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.0.4
• Fix Version/s: JCR Resource 2.0.4
• Component/s: JCR
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 17/Dec/08 19:35
• Updated: 13/Sep/09 13:22
• Resolved: 17/Dec/08 19:37

Description

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.