Hi Joanne,
Do you have the bug reference number for this?
Cheers,
Sarah.
Cornwall Council
Sarah,
It was a while ago and I'm having trouble sorting out my ESRI Support emails for that period. We were dealing with a number of different issues at the same time and some back-and-forths about one problem got mixed up with other problems, etc.
I believe the proper bug reference number for this is: NIM085692 "When an ArcGIS Server is configured with multiple reverse proxies, some of the URLs returned by the server are incorrect"
It's problem description references the following thread: http://forums.arcgis.com/threads/66787-Multiple-Reverse-Proxies, which I was also involved in and really discusses some of the underlying issues. They also noted, in the NIM Problem Desciption, that they were able to reproduce the behaviour I was seeing but there are a number of internal (likely test) server links in the description that I can't imagine they'd appreciate me posting to a forum thread. The problem goes beyond what is described in the forum posts in that if affects a number of links (login, gettoken, help, soap, etc.) in the ArcGIS Services REST pages. So, while I won't include the links they did, here is the rest of the content of their problem description:
I can reproduce this reported behavior when reverse-proxies are configured for ArcGIS Server 10.1 SP1.
<internal url>In this case <internal url> is a reverse proxy for <internal url> and <internal url> is reverse-proxy for <internal url>
Some of the links (login, gettoken, api reference, help, soap, in the services directory page shows a URL with both X-FORWARDED-* hosts instead of using the first one in the comma separated list.
<internal url>
Tokens services and soap url are incorrect in rest/info resource as well.
<internal url>
{
"currentVersion": 10.11,
"fullVersion": "10.1.1",
"soapUrl": "<internal url>",
"secureSoapUrl": null,
"authInfo": {
"isTokenBasedSecurity": true,
"tokenServicesUrl": "<internal url>",
"shortLivedTokenValidity": 60
}
}
As described in the forum post, the soap:address location is incorrect as well.
<internal url>
Unfortunately, we still are on 10.1 SP1 in our production environment, so I'm afraid I can't say if this problem has been addressed in later ArcGIS Server releases. If you find out, I'd be happy to hear about it. It might help push our request to upgrade through our approvals process.
Good luck,
jtm