I’ve just set up some secured cached map services on my ArcGIS Server V10.5.1 and converted my JavaScript API websites to dot net V4.5, upgraded the ESRI JavaScript version to V3.28, and set them up to use the dot net proxy page to handle the username and password process of my secure services.
At first all seemed to be working fine but then I noticed random login boxes appearing asking me to login to the secured map service when I launched the sites. If I simply refreshed the browser the site loads fine, but I can’t have the public experiencing that. It doesn’t appear often, but clearly it shouldn’t appear at all.
The random login box popup was appearing when using the Proxy build version 1.1.0, so I tried changing to the latest proxy page version 1.1.2. Again, at first all seemed fine and the login box appeared to have gone away, but now I have a new random problem. Now my sites randomly don’t load. If I open the Developer Tools Console on the browser I see the error “Failed to load resource: the server responded with a status of 500 (Internal Server Error)” as it’s using the proxy to access the secured map. Again, if I refresh the browser/app the site loads normally and will continue to work fine.
So at the moment I have put the proxy page back to V1.1.0 as I prefer to have a login box error popup than the 500 Internal Server Error message. I’ve tried it and seen it happen on my home PC, so I know it’s not a problem with my work environment.
What am I doing wrong? I can’t track it down, it seems like if the site isn’t used for a while the proxy page fails to work, but if I try again then it does – it doesn’t make sense to me, that’s why I’m asking the forum for help.
I found a post from someone else but it goes back a few years, someone suggested increasing the lifespan of short lived tokens – that didn’t help them and I’ve tried that and it hasn’t helped me either. Has anyone experienced this and found a solution? Thank you,
Mark.
