POST
|
We're experiencing the exact same problem. Glad to hear it will be addressed in 10.1 SP2. Can you provide any more details on how it's going to be addressed? Will it strip down the comma-separated values from X-Forwarded-Host and use only one value (looks like using only the first value is the right thing to do, at least in my case). I'm really pleased that AGS 10.1 is trying to be smart about returned URLs in JSON (and other) responses - it's a bit improvement over the "virtual directories" that had to be hand-built in 10.0 and earlier. I just wish that (1) it was better documented (I discovered this behavior entirely accidentally) and (2) was just a little bit smarter about the comma-separated values. The WebContextURL isn't a good solution for us since it appears to be server-wide, not per-service. David
... View more
06-03-2013
07:02 AM
|
0
|
0
|
1292
|
POST
|
Shaun: Did you ever get any satisfactory resolution on this? We're dealing with the same issue, where we can't find a place to modify the URL that's returned in JSON output from ArcGIS Server map export requests. I have discovered, entirely accidentally, that ArcGIS Server 10.1 can automatically change that URL for you, to match the URL that you used to make the original export request. We have a couple of reverse proxy servers and firewalls in front of our ArcGIS Server (AGS) box, but enough of the original export URL seems to be getting to AGS for it to change the URL in the JSON output to match. I'll speculate that the info is coming in on the HTTP headers, so your reverse proxy(s) probably needs to preserve those. In our case the URL in the JSON is a bit mangled right now, but is very close. Working to fix that now. I sure wish this behavior was documented somewhere. Anyone? David
... View more
05-24-2013
07:09 AM
|
0
|
0
|
440
|
POST
|
I've got a hand-built page layout, using CSS to create a header, left and right sidebars, a footer, and a large main section in the middle out of div tags. With FF, Chrome, and IE8.0.7600 it works great. With IE8.0.6001 and IE7, when the esri.Map function is called, the rendering of the page gets all messed up. The size of the main center section changes, content in the header shows up on top of the left sidebar, and the style color information is lost for the header and sidebars. Only the footer remains unmolested. If I use <meta http-equiv="X-UA-Compatible" content="IE=8"> then it works fine in both versions of IE8. Rendering is still messed up in IE7. The strange part is that the rendering of the page in all above browsers is FINE until the call to esri.Map. Any suggestions? I don't like locking in the rendering with the meta tag, and strictly speaking I shouldn't have to use it for IE8, anyway. Edit: Forgot to say that I get the same results with JS API 2.0 and 2.1. David
... View more
11-17-2010
09:50 AM
|
0
|
0
|
422
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|