Default legend widget does not work over https in IE

[BenSayers]

When using the default ESRI widget the legend symbology do not show up when using Internet Explorer (IE). They show fine in Chrome, Safari and Firefox, but when using IE this all that is displayed is the browser standard red x's.

I have seen others having the same trouble in various different posts and some people have suggested various fixes for previous versions of the API, but none work for me. I am using AGS 10.04 and JS API v2.8.

Has anyone fixed this exact problem? Anyone at ESRI looked in to this?

Any help/suggestions will be greatly appreciated.

In anticipation, Ben.

[derekswingley1]

It appears that I am using Base64, as the requests for my images in Internet Explorer look like: https://www.efafrica.com/rest/services/EFAv3/EFA_Mainv3/MapServer/1/images/3b55578f
How do I force the actual image request rather that the Base64?

The API handles this for you by doing what the browser supports. In IE, that means using the image file instead of base64 encoded data. You should not have to do anything.

Coincidentally, once I have right-clicked on the red x image and copied the image URL then logged in through the ArcGIS Server REST API Login screen that one image appears in the legend but none of the others, would you expect this to happen?
I feel we are getting a little closer to solving the problem<snip>

I think so too, but I'm out of ideas. Can you open a ticket with support so they can take a look at how your service is configured? If I think of anything else or have additional suggestions I'll post here.

[derekswingley1]

Just to pile on, i can replicate this as well.  On my secure service (entire app is secure, so layers are not), the legend shows red x's in IE only

The non base64 encoding is definitely the difference.

The source path to the image in the legend is not getting the token appended on it

If i sniff the token using fiddler, and then append the ?token=LqGIFsRUz8nkeM3XKjYT4W1U0xfLvBT7cEkYZcT3jZU. to the end of the image request in IE for the legend the legend item appears.

Jeff�?? are you on 2.8 as well?

[JeffPace]

Jeff�?? are you on 2.8 as well?

yes i am, but i just test 2.5 2.6 2.7 and they all exhibit the same behavior in IE only.

I also am using a .jsp proxy and have ArcGIS Server for JAVA 10ps4

[derekswingley1]

I also am using a .jsp proxy and have ArcGIS Server for JAVA 10ps4

Maybe this is an issue with the .jsp proxy as that's what both you and Ben are using. My testing has been with the .net proxy. Can you open a ticket with support as well?

[BenSayers]

@Derek: Can you test with a .jsp proxy your end? Would be good to eliminate this.

I'll have to open a ticket with ESRI(UK) who no doubt will pass it straight to the US.

[JeffPace]

I can next week in the middle of Cityworks at the moment.

Would be beneficial if esri could test against proxy.jsp and a JAVA base install.

[derekswingley1]

Would be beneficial if esri could test against proxy.jsp and a JAVA base install.

Let me see what I can do...might take a bit of searching to find a Java instance configured with SSL and appropriate services.

[JeffPace]

Let me see what I can do...might take a bit of searching to find a Java instance configured with SSL and appropriate services.

https://www.mymanatee.org/arcgis/rest/services/utilities-infrastructure/irrigation/MapServer/

u: esri
p: esri

Secure service with https required.  Running on Arcgis Server 10ps4 for JAVA on windows. 

hope that helps.

[derekswingley1]

Thanks Jeff.

That URL redirects to what looks like a resource on your local network and 404's for me. Here's the redirect URL I'm seeing:  https://mcg-ap-arcsvr02.mcgad.local:8343/arcgis/rest/login?redirect=https%3A%2F%2Fwww.mymanatee.org%...

[JeffPace]

Thanks Jeff.

That URL redirects to what looks like a resource on your local network and 404's for me. Here's the redirect URL I'm seeing:  https://mcg-ap-arcsvr02.mcgad.local:8343/arcgis/rest/login?redirect=https%3A%2F%2Fwww.mymanatee.org%...

That is an annoying side effect of our WebAppFirewall.  You should be able to consume the resource in a web app. 

https://www.mymanatee.org/arcgis/rest/services/utilities-infrastructure/irrigation/MapServer/?token=....

not sure how long that token is good for.