Select to view content in your preferred language

Register protected Service with URL containing non-ascii or encoded non-ascii characters

415
2
08-30-2024 03:42 AM
Status: Open
JonasLeksell2
Occasional Contributor

Recently found a problem with registering ArcGIS Server service with Portal for ArcGIS where the service had been published with a non-ascii character like the Swedish Å Ä or Ö causing the service URL to contain translations of those chars to %C3%B6 representing the character ‘ö’ or %C3%A4 representing character ‘ä’.

There was no problem consuming the service in ArcGIS Pro or MapViewer in the Portal for ArcGIS, but when we tried to register the service with the portal saving the credentials, we got an error that mentioned invalid URL as the reason.

However, ArcGIS Enterprise has no other problems with managing services having åäö in the service name or service folder. We have lots of server folders and services using dose characters, causing URL´s with the same encodings. The problem seems to be isolated to one specific function, the proxy function when registering protected services.

I guess that the Portal for ArcGIS Proxy function is not configured to accept Unicode URL strings or encoding that occurs to manage them.

My IDEA or “enhancement request” is that what ever it is that causes the Portal proxy function to fail to manage dose URL´s is reconfigured to support the encoding of Unicode URL strings and the encoded URL string.

Tags (3)
2 Comments
JeffSmith

@JonasLeksell2 You are right; that should not be happening.  I would recommend contacting Support to get a bug logged for that.

JonasLeksell2

Hi Jeff,

In contact with the supportservice it became apparent to me that I was not clear enough in the IDEA. We have not tried to enter a correct encoded URL string when registering the service. I have corrected at the end that I would like the proxy function to be able to manage Unicode URL:s as well as the encoded string.

It could be that the problem I have seen is that the proxy never tried to manage the given URL string as an encoded string, instead used the raw text field as I entered it. Still, I think that this is a faulty management as to get to the save credentials there are actually communications with the service, so an encoded (validated) string exists within that workflow that could be used.

Regards,
Jonas