404 From The Web Adaptor When Passing Long JSON Requests?

1398
3
08-17-2011 01:40 AM
JithenSingh
Esri Contributor
Hi There,

I am experiencing a rather weird issue.
I have ArcGIS Server 10.1 configured and running with two URL assigned to the server.

1. s5.demos.eaglegis.co.nz --> Setup to use IIS and port 80
2. sandbox.demos.eaglegis.co.nz --> Setup to use the inbuilt web server and port 6080

When I pass this request DIRECTLY to the server so it's using the inbuilt server on port 6080 (yes the URL below does not have the port 6080 because a reverse proxy is automatically redirecting requests), it works as expected:

http://sandbox.demos.eaglegis.co.nz/arcgis/rest/services/Utilities/ExportWebMap/GPServer/Export%20We...{%0D%0A++++%22baseMap%22%3A+{%0D%0A++++++++%22title%22%3A+%22Shared+Imagery+Basemap%22%2C%0D%0A++++++++%22baseMapLayers%22%3A+%5B%0D%0A++++++++++++{%0D%0A++++++++++++++++%22url%22%3A+%22http%3A%2F%2Fapps.wcc.govt.nz%2Farcgis%2Frest%2Fservices%2FBasemap%2FAerial_Photo%2FMapServer%22%0D%0A++++++++++++}%0D%0A++++++++%5D%0D%0A++++}%2C%0D%0A++++%22exportOptions%22%3A+{%0D%0A++++++++%22dpi%22%3A+96%2C%0D%0A++++++++%22outputSize%22%3A+%5B%0D%0A++++++++++++1024%2C%0D%0A++++++++++++768%0D%0A++++++++%5D%0D%0A++++}%2C%0D%0A++++%22layoutOptions%22%3A+{+++++++++++++++%22copyrightText%22%3A+%22Copyright+%C2%A9+2011%2C+Eagle+Technology+Group+Ltd%22%0D%0A++++}%2C%0D%0A++++%22mapOptions%22%3A+{%0D%0A++++++++%22extent%22%3A+{%0D%0A++++++++++++%22xmin%22%3A+1740705.1748995285%2C%0D%0A++++++++++++%22ymin%22%3A+5425832.984404932%2C%0D%0A++++++++++++%22xmax%22%3A+1759010.1448428018%2C%0D%0A++++++++++++%22ymax%22%3A+5431133.128338553%2C%0D%0A++++++++++++%22spatialReference%22%3A+{%0D%0A++++++++++++++++%22wkid%22%3A+2193%0D%0A++++++++++++}%0D%0A++++++++}%0D%0A++++}%2C%0D%0A++++%22operationalLayers%22%3A+%5B%0D%0A++++++++{%0D%0A++++++++++++%22url%22%3A+%22http%3A%2F%2Fs3.demos.eaglegis.co.nz%2FArcGIS%2Frest%2Fservices%2FRoadshow%2Foverlays%2FMapServer%22%2C%0D%0A++++++++++++%22title%22%3A+%22Overlays%22%2C%0D%0A++++++++++++%22opacity%22%3A+0.7%2C%0D%0A++++++++++++%22visibleLayers%22%3A+%5B%0D%0A++++++++++++++++1%0D%0A++++++++++++%5D%2C%0D%0A++++++++++++%22showSublayerLegends%22%3A+%5B%0D%0A++++++++++++++++1%0D%0A++++++++++++%5D%0D%0A++++++++}%2C%0D%0A++++++++{%0D%0A++++++++++++%22url%22%3A+%22http%3A%2F%2Fs3.demos.eaglegis.co.nz%2FArcGIS%2Frest%2Fservices%2FRoadshow%2Fsculpturesandtracks%2FMapServer%22%2C%0D%0A++++++++++++%22title%22%3A+%22Sculptures+And+Tracks%22%2C%0D%0A++++++++++++%22opacity%22%3A+0.7%2C%0D%0A++++++++++++%22showSublayerLegends%22%3A+%5B%0D%0A++++++++++++++++0%2C%0D%0A1%0D%0A++++++++++++%5D%0D%0A++++++++}%0D%0A++++%5D%0D%0A}&Layout_Template=Roadshow&Format=PDF&env%3AoutSR=&env%3AprocessSR=&f=json&_=1313573193992

When I pass the SAME request to via the web adaptor, I get a 404 being returned. IIS is setup to use default settings with nothing extra. All other JSON requests via the web adaptor seem to work fine.

http://s5.demos.eaglegis.co.nz/arcgis/rest/services/Utilities/ExportWebMap/GPServer/Export%20Web%20M...{%0D%0A++++%22baseMap%22%3A+{%0D%0A++++++++%22title%22%3A+%22Shared+Imagery+Basemap%22%2C%0D%0A++++++++%22baseMapLayers%22%3A+%5B%0D%0A++++++++++++{%0D%0A++++++++++++++++%22url%22%3A+%22http%3A%2F%2Fapps.wcc.govt.nz%2Farcgis%2Frest%2Fservices%2FBasemap%2FAerial_Photo%2FMapServer%22%0D%0A++++++++++++}%0D%0A++++++++%5D%0D%0A++++}%2C%0D%0A++++%22exportOptions%22%3A+{%0D%0A++++++++%22dpi%22%3A+96%2C%0D%0A++++++++%22outputSize%22%3A+%5B%0D%0A++++++++++++1024%2C%0D%0A++++++++++++768%0D%0A++++++++%5D%0D%0A++++}%2C%0D%0A++++%22layoutOptions%22%3A+{+++++++++++++++%22copyrightText%22%3A+%22Copyright+%C2%A9+2011%2C+Eagle+Technology+Group+Ltd%22%0D%0A++++}%2C%0D%0A++++%22mapOptions%22%3A+{%0D%0A++++++++%22extent%22%3A+{%0D%0A++++++++++++%22xmin%22%3A+1740705.1748995285%2C%0D%0A++++++++++++%22ymin%22%3A+5425832.984404932%2C%0D%0A++++++++++++%22xmax%22%3A+1759010.1448428018%2C%0D%0A++++++++++++%22ymax%22%3A+5431133.128338553%2C%0D%0A++++++++++++%22spatialReference%22%3A+{%0D%0A++++++++++++++++%22wkid%22%3A+2193%0D%0A++++++++++++}%0D%0A++++++++}%0D%0A++++}%2C%0D%0A++++%22operationalLayers%22%3A+%5B%0D%0A++++++++{%0D%0A++++++++++++%22url%22%3A+%22http%3A%2F%2Fs3.demos.eaglegis.co.nz%2FArcGIS%2Frest%2Fservices%2FRoadshow%2Foverlays%2FMapServer%22%2C%0D%0A++++++++++++%22title%22%3A+%22Overlays%22%2C%0D%0A++++++++++++%22opacity%22%3A+0.7%2C%0D%0A++++++++++++%22visibleLayers%22%3A+%5B%0D%0A++++++++++++++++1%0D%0A++++++++++++%5D%2C%0D%0A++++++++++++%22showSublayerLegends%22%3A+%5B%0D%0A++++++++++++++++1%0D%0A++++++++++++%5D%0D%0A++++++++}%2C%0D%0A++++++++{%0D%0A++++++++++++%22url%22%3A+%22http%3A%2F%2Fs3.demos.eaglegis.co.nz%2FArcGIS%2Frest%2Fservices%2FRoadshow%2Fsculpturesandtracks%2FMapServer%22%2C%0D%0A++++++++++++%22title%22%3A+%22Sculptures+And+Tracks%22%2C%0D%0A++++++++++++%22opacity%22%3A+0.7%2C%0D%0A++++++++++++%22showSublayerLegends%22%3A+%5B%0D%0A++++++++++++++++0%2C%0D%0A1%0D%0A++++++++++++%5D%0D%0A++++++++}%0D%0A++++%5D%0D%0A}&Layout_Template=Roadshow&Format=PDF&env%3AoutSR=&env%3AprocessSR=&f=json&_=1313573193992

Does anyone have some ideas as to why this is happening? Been running a few tests but the web adaptor keeps returning this very weird 404. The inbuilt web server seems to work fine. BTW the JSON above executes a ExportWebMap for a layout that I have setup on the server.

Thanks!
0 Kudos
3 Replies
RaviNarayanan
Esri Contributor
Jithen,

this is limited by the maximum request length limit set in IIS. You can increase this using the IIS request filtering max url length setting shown in the screenshot.

0 Kudos
JithenSingh
Esri Contributor
Of course the max url strength. Totally slipped my mind. Thank you for this.
Maybe this should be noted in the documentation. Many users might struggle with this is as the URL's grow.

Cheers

Jithen,

this is limited by the maximum request length limit set in IIS. You can increase this using the IIS request filtering max url length setting shown in the screenshot.

0 Kudos
MapEnglish
Occasional Contributor
I came across this issue as well doing dynamic layer requests. I agree, it would be useful to have this noted in the web adaptor doc.

Cheers,
Matt English
Esri Canada
0 Kudos