AnsweredAssumed Answered

ArcGIS Server ETag header in single machine high-availability active-active configuration

Question asked by NicolasGIS on May 23, 2018



In a single-machine-high-availability-active-active-deployment, though 2 webservices are exactly identical (same SDE geodatabase), but also identical:

- MapServer info json : https://x.y.z/arcgis/rest/services/Folder/Service/MapServer/?f=json  

- Layer info json : https://x.y.z/arcgis/rest/services/Folder/Service/MapServer/layers?f=json 

- Legend info json : https://x.y.z/arcgis/rest/services/Folder/Service/MapServer/legend?f=json 

- Admin info json https://x.y.z/arcgis/admin/services/Folder/Service.MapServer?f=json

except the name of the host (extension["properties"]["appSchemaURI"], extension["properties"]["onlineResource"]),

I keep having 2 different ETag header for the same request preventing the user from using its cached answer. 

Is there anything I overlooked or is that a limitation of a single-machine-high-availability scenario ?


Thanks !