[SLING-9777] Better handling for invalid URIs when using SlingUri (special characters, spaces)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: API 2.23.0
• Fix Version/s: API 2.23.4
• Component/s: API
• Assignee: Georg Henzler
• Reporter: Georg Henzler
• Created: 30/Sep/20 18:28
• Updated: 04/May/21 10:36
• Resolved: 08/Oct/20 21:29

Description

SlingUri should not "have an opinion" about when URIs should be encoded or not. It should be able to deal with invalid URIs in a best effort manner (e.g. URIs containing a space in the path are already invalid) and always try to not change the identity of the URI (means: UriBuilder.parse(inputStr,null).build().toString() should almost always be equal to the original inputStr). This also means if the SlingUri contains escape sequences (e.g. %20), it should keep them, if escape sequences are unescaped already this is also fine when using the builder (when using parse() this can lead to invalid URIs, best effort parsing shall be used for those cases).

Issue Links

• is related to: SLING-9745 Introduce SlingUri API to simplify creation/manipulation of Sling URIs