I am unable to successfully submit an ASP.NET web form when a large number of RadListBox items are selected (79 in this case). However, if I select a significantly smaller number of items, I am able to successfully submit the form. After consulting with a firewall SME, I was able to verify that the following parameter was causing the "network security engine" to reject the request: "radListBox_ID_ClientState={"logEntries":[{"Type":1,"Index":"1","Data":{"value":"6","selected":false,"text":"TextValue_1"}},{"Type":1,"Index":"2","Data":{"value":"15","text":"TextValue_2"}},...,{"Type":1,"Index":"79","Data":{"value":"101","text":"TextValue_79"}},"}}],"selectedIndices":[0],"checkedIndices":[],"scrollPosition":1629}.
Obviously, the payload for this parameter is significantly large. Consequently, the network "network security engine" exceeded its set number of maximum recursions to verity the content of this parameter was not malicious. Therefore, the request was rejected when a user selected a large number of items via RadListBox control, causing a page error. Is there a known work around for this issue? Is there a way to reduce the payload when submitting a form with a large number of RadListBox items are selected (e.g., > 100)? Thanks in advance!
1 Answer, 1 is accepted
Looking at the ClientState value I see that the problem is not the selected items, but the LoadOnDemand mode you are using. These values: {"Type":1,"Index":"1","Data":{"value":"6","selected":false,"text":"TextValue_1"}} represent a node added through WebService and are needed in order to notify the server of the new node.
Unfortunately there isn't a way to decrease the size of the client state in this scenario. The only solution to this issue is to use another LoadOnDemand mode ( see the following demo)
http://demos.telerik.com/aspnet-ajax/listbox/examples/functionality/loadondemand/defaultcs.aspx
Hope this was helpful.
Kind regards,
Bozhidar
the Telerik team