setInternalPath URI encoding
Updated by Wim Dumon almost 8 years ago
- Status changed from InProgress to Resolved
I took a look at this and we currently only seem to escape the necessary characters from the URL: %, , ' ', # and &. I'm afraid that without these, we may have problems to convert an URL unambiguously when it is entered in the address bar by the user. '', being an alternative for '%20', is problematic to decode unambiguous in our 'ugly' implementation of the internal paths (when your wt application is deployed on '/', with the query string encoded path).