You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Set up a ESRI data source with many layers. One example is the Australian
Department of Environment with the cva_national map.
2. Set the data source to be fairly long as this gets added to all the layer
names making the request larger. "sewpac" was OK by "ts-sewpac" was not for the
cva_national layer group.
3. Try to load the cva_national layer group.
What is the expected output? What do you see instead?
The layers should load OK in the client but instead only "Loading ..." is shown
when the user clicks on the layer.
When using the developer tools to look at the AJAX error we get:
Request Entity Too Large
The requested resource
/atlasmapper/public/layersInfo.jsp
does not allow request data with GET requests, or the amount of data provided
in the request exceeds the capacity limit.
The AJAX request appears to include all the sublayers in the request, pushing
it over the limit, which appears to be < 7.5KB.
What version of the product are you using? On what operating system?
1.4.6, Linux server, Chrome client.
Please provide any additional information below.
AJAX request for layer info looked like.
http://maps.e-atlas.org.au/atlasmapper/public/layersInfo.jsp?client=ts&layerIds=
ts-sewpac_marine%2Fcva_national%2F5_Commonwealth%20Marine%20Reserves%20-%20outer
%20boundaries%20July%202013,ts-sewpac_marine%2Fcva_national%2F6_Commonwealth%20M
arine%20Reserves%20-%20July%202013,ts-sewpac_marine%2Fcva_national%2F7_Ramsar%20
Wetlands,ts-sewpac_marine%2Fcva_national%2F8_World%20Heritage%20Areas,ts-sewpac_
marine%2Fcva_national%2F12_Black%20noddy,ts-sewpac_marine%2Fcva_national%2F13_Bl
ack-naped% ....
Original issue reported on code.google.com by [email protected] on 22 Oct 2013 at 12:43
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 22 Oct 2013 at 12:43The text was updated successfully, but these errors were encountered: