Latest Contributions by JeffPace

arcgis/rest/info does not resolve to the server that has the security on it.  We only allow access to the sub folder. { "currentVersion": 10.03, "soapUrl": "http://mcg-ap-arcsvr02:8399/arcgis/services", "secureSoapUrl": "https://mcg-ap-arcsvr02:8343/arcgis/services", "authInfo": {   "isTokenBasedSecurity": true,   "tokenServicesUrl": "http://MCG-AP-ARCSVR02:8399/arcgis/tokens" } } ... View more

yes its token based, it is behind a web application firewall (modproxy). arcgis/rest/info does not resolve to the server that has the security on it.  We only allow access to the sub folder. ... View more

What kind of security are you using? I was assuming you were using token based but /ArcGIS/info says that's not enabled:  http://www.mymanatee.org/arcgis/rest/info?f=pjson { "currentVersion": 10.03, "soapUrl": <snip> "secureSoapUrl": <snip> "authInfo": {"isTokenBasedSecurity": false} } yes its token based, it is behind a web application firewall (modproxy). ... View more

anything else i can test in the meantime? 2.5 works perfectly.  2.6 no call is being made to token service its public now https://www.mymanatee.org/gisapps/mapviewer/index.jsp?type=utilitiesinfrastructure <removed> for username and password. ... View more

Looking forward to what you find. anything else i can test in the meantime? ... View more

Do you see a call to /ArcGIS/info when you load your page? You should see this in firebug or chrome dev tools. You can see this in our identity manager sample:  https://servicesbeta.esri.com/demos/widget/widget_identifymanager.html I can't test at the moment.  This is our production server and it is in use, and unfortunately we do not have a development environment to support ssl so we have to deploy to test (i know, worst business practice). Once the field guys are done for the day i will roll production back to 2.6 and test. ... View more

Hmm, having trouble I get garbage back.    �  This is a secure service (obviously) with ssl enabled. I tried that same like on my server that does not have security, and it only works on port 8343 with same response.  8399 gives page not found, is that correct? ... View more

2.5 tried to guess the tokenServiceUrl but 2.6 does not. Can you post the response from your REST info endpoint? Here's an example using servicesbeta.esri.com:  http://servicesbeta.esri.com/ArcGIS/rest/info?f=json&pretty=true And the response: {   "currentVersion" : 10.02,   "soapUrl" : "http://WEBAPI20BETA/arcgis/services",   "secureSoapUrl" : "https://WEBAPI20BETA:443/arcgis/services",   "authInfo" : {     "isTokenBasedSecurity" : true,     "tokenServicesUrl" : "https://servicesbeta.esri.com/ArcGIS/tokens"   } } Hmm, having trouble I get garbage back.    �  This is a secure service (obviously) with ssl enabled. ... View more

What is version of ArcGIS Server are you using (including service pack)? 10.03 10 service pack 3 for java ... View more

In my app it is possible to issue queries on the same layer in rapid enough succession that the issue of out-of-order execution of the response is an issue.  Is there any way of tagging the queries so they can be identified in the callback?  I saw on the IOS thread that an NSOperation associated with each query can be used for this purpose.  Is there any mechanism in the Javascript toolkit for identifying what query invoked the callback? The only thing I can think to do is to associated each query with a different (identical except that the function itself serves as an id) callback function, but that seems pretty lame. Thanks, Rex Bradford Direct Relief International Instead of different callbacks, why not just pass an additional identifying variable to the callback along with the resultset we do: task.execute(q, dojo.hitch(this, "searchCallback", layerData.name, layerdesc, layerData.titleField)); .  which allows us to use just one callback but have layer dependent functionality. our searchCallback then looks like searchCallback: function(layerId, layerdesc, titleField, featureSet) { ... View more

We're identifying all the layers. (The layer 9 was the original poster's code). Here's a more complete look at what I have: identifyTask = new esri.tasks.IdentifyTask(MyESRISearchUrl);         identifyParams = new esri.tasks.IdentifyParameters(); identifyParams.tolerance = 2; identifyParams.returnGeometry = true; var lids = ""; identifyParams.layerIds = MyESRILayerIDs; lids += " --- "; identifyParams.layerOption = esri.tasks.IdentifyParameters.LAYER_OPTION_VISIBLE; /* LAYER_OPTION_TOP; */ I swapped out LAYER_OPTION_VISIBLE for LAYER_OPTION_ALL and that of course enabled me to see everything.  But I need to find a way to get LAYER_OPTION_VISIBLE working properly (assuming that when anything is visible on the map, I can identify it). We did have some permission issues early on with the service--I believe it's accessible now.  How could the REST API not being publicly accessible make some layers visible/identifiable and some not? Public accessibility wouldn't affect function, but it would allow me to see it to try to help 🙂 ... View more

Right.  And right now we're using: identifyParams.layerOption = esri.tasks.IdentifyParameters.LAYER_OPTION_VISIBLE; So it makes me wonder why I can't detect certain items in the same service when they first become visible.... IS your rest service publicly accessible? It looks like you are only identifying layer 9, and then only if its visible.  Is that correct? ... View more

I'm experiencing a similar issue.  I have a map service with some layers visible at all extents, while other layers are visible only below 1000 ft.  For the layers that are always visible, my click event triggers the identifyTask every time and I get the results I want.  When I get to 1000 ft, I can see the other layers, but the click event doesn't return objects until after I zoom in a couple of more levels.  My assumption is that if I can see the features, I can identify them.  But that's not the case. I don't see any real differences in my code vs. the other code examples in this thread.  Any suggestions? Remember the default is to return only the top layer. identifyParams.layerOption = esri.tasks.IdentifyParameters.LAYER_OPTION_TOP; if you want all its identifyParams.layerOption = esri.tasks.IdentifyParameters.LAYER_OPTION_ALL; or visibile identifyParams.layerOption = esri.tasks.IdentifyParameters.LAYER_OPTION_VISIBLE; if you dont explicitly set it, it is TOP. ... View more

I need to be able to execute geoprocessor tasks to the Rest API with more data than will fit in a GET request. It appears to me that the ArcServer Javascript API uses GET to send the requests to a GPServer no matter if I use proxy.ashx or not. Is this correct? To get around this I wrote a POST based caller with ExtJs that works well. But, now I need this to work on cross domain basis and I have not figured out how to do this with my ExtJs method. I would go back to the Javascript API Execute method if I could get it to use POST. Any ideas? Thanks, Dave if you use esri.request it will automatically switch between get and post as needed.  you could also explicitly use dojo.xhrGET or dojo.xhrPOST.  However, which execute method are you using that is trying to execute a GET with >2000 characters? that should not happen ... View more