POST
|
Mihkel, Did you try without the URIEncoding property set for the tomcat on port 8080? My previous post assumed the service was accessed via port 8399. Ravi, in our case the URLEncoding property for the <connector> port 8080 has to be UTF-8 because we have other REST services on the same webserver separate from ArcGIS services that require UTF-8.
... View more
11-17-2011
10:42 PM
|
0
|
0
|
322
|
POST
|
I managed to get the GET queries to handle accents, but only with secured (https) services. Regular http services still won't handle the accents. Have tried out different configurations for the http port both on Tomcat's and ArcGIS Server Java side, doesn't matter whether the URLEncoding property is set to UTF-8 or not. So, if there are any Tomcat specialists, I'm still interested in getting the damn thing working with regular http. Mihkel
... View more
11-16-2011
11:41 PM
|
0
|
0
|
761
|
POST
|
Mihkel, if the URIEncoding property is set for tomcat HTTP Connector, can you try without this setting? http://tomcat.apache.org/tomcat-5.5-doc/config/http.html For example if this is tomcat that is installed with the server check for the URIEncoding property defined for a <Connector> in \ArcGIS\Server10.0\java\manager\service\managerappserver\conf\server.xml The URLEncoding property is set only for the <connector> port 8080 in \Tomcat6.0\conf\server.xml and this has to be UTF-8. Will setting the URIEncoding for \managerappserver\conf\server.xml <connector> port 8399 or for \managerserver\conf\server.xml <connector> port 8099 affect the processing of GET queries? Mihkel
... View more
10-17-2011
01:10 AM
|
0
|
0
|
761
|
POST
|
Both GET/POST are supported and we want to understand why this may not be working for your case. Is this a .NET or a Java Server. If this is a Java, can you provide information about the applications server that is used? It is an ArcGIS Server 10.0 for the Java Platform SP2 and Tomcat 6.0.32 as the application server. I have to mention that I am not very familiar with configuring Tomcat. So any ideas or tips are more than welcome. Mihkel
... View more
10-11-2011
11:02 PM
|
0
|
0
|
761
|
POST
|
Mihkel, is this 10.0 or a 10.1 beta server? Server version 10.0 SP2. Does the GET method through a REST service support accented characters in queries at all? Mihkel
... View more
10-11-2011
06:58 AM
|
0
|
0
|
761
|
POST
|
Does the locator work in ArcMap? Brad Yes, works just fine in ArcMap. It turns out that the problem not only occurs with locators but with other REST services as well: the query URL-s are encoded nicely to UTF-8 but the servers response is what gives errors - all special characters are handled as "?" within GET queries. POST queries containing special characters are handled nicely, but as far as I know the locator services only support the GET method? Any ideas? Mihkel
... View more
10-11-2011
04:06 AM
|
0
|
0
|
761
|
POST
|
I'm trying to create an address locator to use in an ArcGIS viewer for Flex application. I end up with a locator that does not support accented letters like ö, ä, ü, õ. Doesn't matter wheter I use the service via the Flex application or just query via browser - the locator is unable to process these accents. I have tried with the feature class in a gdb and shapefile, locator in a gdb and in a folder, setting the gdb-s and locators configuration keywords to DEFAULTS (which is UTF-8), installed ArcGIS 10 SP2 (Desktop, Server) Fullwidth Unicode Characters and Conversion Patch both for my PC and Server. Both are running v10 SP2. Still no luck... 😞 Has anybody a clue what might be the problem? Thanks in advance, Mihkel
... View more
10-03-2011
01:16 AM
|
0
|
13
|
1769
|
POST
|
I've migrated from 2.3.1 to 2.4 by copying XML files. The viewer appears to be working fine, except that the busy "clock" icon won't go away. Nate S Same problem here. The busy icon appears when REloading widgets. The viewer works fine, though. :confused: Mihkel H
... View more
08-29-2011
11:07 PM
|
0
|
0
|
316
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|