POST
|
Background: we are upgrading to ArcGIS Enterprise from 10.2.2 to 10.6.1. We use a proxy server direct traffic from www to our ArcGIS Server inside our firewall. We use Web Adaptor on the proxy server. Using our 10.2.2 environment, one can browse the public REST directory using the HTML interface: https://gis.dallascityhall.com/wwwgis/rest/services We have a test DNS set up for our new proxy and server. When you submit the corresponding URL to browse the REST catalog, a 500.52 error is thrown that indicates the URL Rewrite module cannot handle the gzip compression. https://testgis.dallascityhall.com/wwwgis/rest/services The error description in Failed Request logs is: Outbound rewrite rules cannot be applied when the content of the HTTP response is encoded ("gzip").Outbound rewrite rules cannot be applied when the content of the HTTP response is encoded ("gzip"). We are using the same basic rewrite rules as before. However, a what's new article indicates that the content-type for JSON changed at 10.6: The content-types for JSON and JSON with callback responses have been changed from text/plain. For JSON: Content-Type:application/json;charset=utf-8 For JSON with callback: Content-Type:application/javascript;charset=utf-8 If you put a format tag at the end of the URL to indicate output as JSON (?f=json), the query works just fine. Leave off the format tag and you get a 500.52 error. I suspect this has something to do the with content-type changes at 10.6, but I'm not sure what corrective action to take in ArcGIS Server (and presumably Portal) to address the issue. Or, maybe this is not the issue at all. Behavior is the same in Chrome and Edge. IE doesn't know what to do with the URL; it keeps prompting you to Open or Save the services.json file. Both proxy servers are Windows 2012 R2 IIS 8.5. Both have CA Signed certificates and registered domains. The only other major difference is the test DNS (10.6.1 Enterprise) only accepts HTTPS (port 443); HTTP is disabled (port 80). The architecture (other than Enterprise version) is otherwise identical. One other thing. The expires header shows Wed, 31 Dec 1969 18:00:00 CST. I found articles on Apache that indicates it is confidential/private variable setting in the web.xml. But this is IIS, so I am not sure this is related.
... View more
12-14-2018
12:42 PM
|
0
|
0
|
531
|
POST
|
Background: we are upgrading to ArcGIS Enterprise from 10.2.2 to 10.6.1. We use a proxy server direct traffic from www to our ArcGIS Server inside our firewall. We use Web Adaptor on the proxy server. Using our 10.2.2 environment, one can browse the public REST directory using the HTML interface: https://gis.dallascityhall.com/wwwgis/rest/services We have a test DNS set up for our new proxy and server. When you submit the corresponding URL to browse the REST catalog, a 500.52 error is thrown that indicates the URL Rewrite module cannot handle the gzip compression. https://testgis.dallascityhall.com/wwwgis/rest/services The error description in Failed Request logs is: Outbound rewrite rules cannot be applied when the content of the HTTP response is encoded ("gzip").Outbound rewrite rules cannot be applied when the content of the HTTP response is encoded ("gzip"). We are using the same basic rewrite rules as before. However, a what's new article indicates that the content-type for JSON changed at 10.6: The content-types for JSON and JSON with callback responses have been changed from text/plain. For JSON: Content-Type:application/json;charset=utf-8 For JSON with callback: Content-Type:application/javascript;charset=utf-8 If you put a format tag at the end of the URL to indicate output as JSON (?f=json), the query works just fine. Leave off the format tag and you get a 500.52 error. I suspect this has something to do the with content-type changes at 10.6, but I'm not sure what corrective action to take in ArcGIS Server (and presumably Portal) to address the issue. Or, maybe this is not the issue at all. Behavior is the same in Chrome and Edge. IE doesn't know what to do with the URL; it keeps prompting you to Open or Save the services.json file. Both proxy servers are Windows 2012 R2 IIS 8.5. Both have CA Signed certificates and registered domains. The only other major difference is the test DNS (10.6.1 Enterprise) only accepts HTTPS (port 443); HTTP is disabled (port 80). The architecture (other than Enterprise version) is otherwise identical. One other thing. The expires header shows Wed, 31 Dec 1969 18:00:00 CST. I found articles on Apache that indicates it is confidential/private variable setting in the web.xml. But this is IIS, so I am not sure this is related.
... View more
12-14-2018
10:46 AM
|
0
|
0
|
627
|
POST
|
Dwynne from Esri posted a bit of code on another post that might help. Cf.: arcpy.ListRelationshipClasses() | GeoNet
... View more
11-08-2018
07:26 AM
|
0
|
0
|
1798
|
POST
|
Realizing this post is pretty dated, I'm going to respond anyway in case anyone is searching for this topic. When we moved to SQL Server 2012 and introduced the Geometry data type for our SHAPE columns, we also felt some performance pain. Our approach was to tweak the spatial index using native SQL Server approaches. This post summarizes our approach. This was implemented in AGS/EGDB 10.2.2. I am not sure this approach is supported in 10.6. We will be finding out soon.
... View more
07-27-2018
06:11 AM
|
1
|
0
|
625
|
POST
|
I know this is an old post, but this is exactly what I needed to resolve an issue on an old 10.1 ArcGIS Server that needed to be kept running until a migration was completed. Thanks!
... View more
05-10-2018
10:34 AM
|
0
|
0
|
1078
|
POST
|
I'm a bit late to this post, but my experience using the approach that you outline has one main problem - you have to shut down the service to rebuild the locators. However, if the locators are in an Enterprise GDB, that is not the case. When this discussion was taking place, Bug NIM-099335 was just a few months old. Almost a year since this bug was reported, it is still an issue (for 10.2.2.). It's frankly frustrating to have to implement a complicated workaround for something that could be accomplished two versions prior (10.0). I totally get that file GDB is a single-user data set and enjoys less overhead, etc. But shutting down services to rebuild indices is inefficient if you like to automate such tasks (I do). Incidentally, I'm not rubbishing your suggestion - it's a great way to avoid the issues involved in this bug and like I said, I do use it in production. But, my goal when upgrading to 10.2.2. was to automate as much as possible and shutting down services requires a password to be passed - which implies that to script it, it has to be stored somewhere. Yes, there are ways to encrypt, etc., but all of this to avoid a bug that has been on the books for almost a year. Sorry, Esri, if this has been fixed and I've missed it. But the bug report says it's still open. Cheers.
... View more
02-13-2015
08:19 AM
|
0
|
0
|
1037
|