I am trying to troubleshoot an HTTP POST of a large intersect query on a geometry collection with just over 27000 geometries. The result is that I get back the HTML page for Intersect stating that:
'geometries' must be specified
'geometry' must be specified
The POST data (with a content length of 15301985 bytes) is being lost along the way. When I send more reasonable and sane geometry collections, no problems. The service behaves as expected.
There is obviously, a maximum, but I don't know where in the system it is. And is configurable?
Here's the failed WireShark capture (on port 6080):
And here's a successful one for comparison (on port 6080):
I also observe similar behavior with http://sampleserver3.arcgisonline.com.
Additional info:
أكثر...
'geometries' must be specified
'geometry' must be specified
The POST data (with a content length of 15301985 bytes) is being lost along the way. When I send more reasonable and sane geometry collections, no problems. The service behaves as expected.
There is obviously, a maximum, but I don't know where in the system it is. And is configurable?
Here's the failed WireShark capture (on port 6080):
And here's a successful one for comparison (on port 6080):
I also observe similar behavior with http://sampleserver3.arcgisonline.com.
Additional info:
- The large geometry collection are simple polygon geometries (nothing more than 6 or 7 vertexes per poly).
أكثر...