2

ArcGIS 10.2 Server enforces case sensitivity on map service URLs. This has been the case for some URLs in previous versions but was reported as bugs?

Does anyone know the reason WHY ESRI makes AGS URLs case sensitive? I don't see the logic on making URLs case sensitive as it just adds another layer of unnecessary complexity and adds confusion..

Example of URL that will not work: http://services.arcgisonline.com/arcgis/rest/services/world_street_map/mapserver (incorrect case on service name)

More information: http://blogs.esri.com/esri/arcgis/2013/12/17/esri-basemap-system-upgrade-to-arcgis-10-2-for-server/

5

I am not 100% sure but my educated guess is: it is because the ArcGIS Server core is based on TomCat web server which is case-sensitive in its nature. I believe it was possible to change the case-sensitivity of all urls in TomCat of earlier versions but am pretty sure it is hard to do in the current version used behind the scene in ArcGIS Server 10.1+.

Using a Web Adaptor with a web server where you could have case-insensitive links does not solve the problem (or better to say does not alter this behaviour) since the URLs will be anyway redirected to TomCat used in ArcGIS Server. So, you just have to use case-sensitive notation for your URLs.

If you have some time and want to play with the settings, go ahead to C:\Program Files\ArcGIS\Server\framework\runtime\tomcat. TomCat documentation is here. However, keep in mind that editing the underlying TomCat settings is discouraged and may result in corrupted installation of ArcGIS Server. Esri does not support these workflows so you will not get any support on this. And please never do any of this in production, set up a sandbox machine for testing.

  • 1
    Yeah, a google search of "tomcat case sensitive" brings up a ton of hits. One of interest is the official doc from Apache: tomcat.apache.org/tomcat-7.0-doc/config/context.html (find: allowLinking ). See the note about case and "security problems" if changed. – KHibma Dec 18 '13 at 15:01
  • 1
    Another consideration (although relatively minor) is performance of routing the massive amounts of HTTP requests a system like AGOL receives. If you have to convert every single request to lowercase as part of your routing logic, that starts to add up. – brichins Mar 6 '14 at 17:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.