AGOL thinks service is secured

[MilesWacker]

We have a public map service at:
http://app.mdt.mt.gov/arcgis/rest/services/RIM/MDT_BOUNDARIES_931/MapServer

When this is added to My Content as an "ArcGIS Server web service" we get a message:
"A secure service was detected."

And it asks for a user and password.  This is not a secured service.  Is this a bug or something in our proxy setup?

[MikeMinami]

I can reproduce the problem. We'll need to look at it.
Note, you can add this directly to a web map from the Add menu option when viewing the map.

Thanks,

Mike

[MilesWacker]

I entered a support incident for this.

Thanks

[MikeMinami]

The problem appears to be on your side. Perhaps your web server is set up to block programmatic access to the server?  ArcGIS Online sends this request to your server to gather information.

http://www.arcgis.com/sharing/checkUrl.jsp?url=http%3A//app.mdt.mt.gov/arcgis/rest/services/RIM/MDT_...

The response from the server is:

{"secured": true,"httpStatusCode": 403,"httpStatusMessage": "HTTP/1.1 403 Forbidden","httpResponse": "","url": "http://app.mdt.mt.gov/arcgis/rest/services/RIM/MDT_BOUNDARIES_931/MapServer?f=json"}

When the URL to the service is entered directly in the web browser, it works fine.

http://app.mdt.mt.gov/arcgis/rest/services/RIM/MDT_BOUNDARIES_931/MapServer

Thanks,

Mike

[MilesWacker]

Then why does this return fine:
http://app.mdt.mt.gov/arcgis/rest/services/RIM/MDT_BOUNDARIES_931/MapServer?f=json

That error is generated by the .jsp page, not our rest service.

How would you "Block programmatic access"?

[MikeMinami]

You are correct. The problem is on our side. We're looking at it.

Thanks,

Mike

[MilesWacker]

Anything here?

[MikeMinami]

Actually, we did debug this and found that your server is returning a 403 forbidden message when we attempt to connect from our API. Our developers asserted that there could be some rule set up on your web server that prohibits connections like this. From the browser, the connection is allowed.  Perhaps you can investigate how your web server is configured with this regard. 

We have made a change on our side to ignore this error in this case. It will be released in December.

Thanks,

Mike

[MilesWacker]

Our proxy was blocking Jakarta user-agents.