Closed adgiles closed 11 years ago
It is difficult for the viewer code to automatically know if the encoding is needed or not. Currently I think we always encode, assuming that the database stores things unencoded. The current solution is to store things unencoded.
This is a common issue people bring up in the forums (as Anthony has pointed out). Is it not as simple as doing a RegEx to look for encoding and if there is already encoding applied just skip that step in the APIs handling of the url?
This would need to be fixed in the API, we'll take a look at it for 3.6.
This has been fixed in the API and will be available in the next release.
When a URL with special characters is encoded in the pop up, extra characters are added which breaks the link, I.e. %20 which denotes a space become %2520 as the % sign is encoded to its HTML value of %25. This also happens to other characters such as ? and & which are found in many URLs particularly ones from sharepoint lists etc..
See reporting on the forums:
http://forums.arcgis.com/threads/93130-URL-link-encoding
http://forums.arcgis.com/threads/65738-Identify-Widget-3.0-gives-different-url-for-popup-and-results
http://forums.arcgis.com/threads/90595-Hyperlink-in-a-pop-up
http://forums.arcgis.com/threads/83093-pop-up-hyperlinks-not-working-spaces-getting-translated-to-2520
Thank you
Anthony