Unable to use Umbraco.MultiNodeTreePicker with a lot of picked values

[PeterKvayt]

Which Umbraco version are you using?

15.3.0

Bug summary

I have content "Foo" with Umbraco.MultiNodeTreePicker property. I add many nodes (77) into this property programmatically.
While I am opening the "Foo" content, I am facing the error "The request filtering module is configured to deny a request where the query string is too long.":

As you can see, I am using the IIS server, and the request is not matching to its defaults. I can increase the request length, but as you can see, it is not secure.

I think we should change the request from GET with a long parameters list to something else, maybe POST with json payload or we should provide paging for Umbraco.MultiNodeTreePicker (I think it will be the best solution). It will fix the problem with the request length and also the rendering problem with a huge amount of picked content.

Specifics

Use default IIS server for testing

Steps to reproduce

1. Fresh umbraco install
2. Create Doc Type "TestDocType" with Umbraco.MultiNodeTreePicker property
3. Create content node from "TestDocType"
4. Fill the content's property with a lot of values (77 or more).
5. Try to open the content node

Expected result / actual result

Expected: there is no error in logs, and there is no notification error
Actual: there is an error inthe console log and "Api error"

---

This item has been added to our backlog AB#51345

[github-actions]

Hi there @PeterKvayt!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[Bartosz97]

yes, I can confirm the same problem. For GET request, query is too long. I've changed configuration on web.config file but it is workaround:
<system.webServer> <security> <requestFiltering> <requestLimits maxQueryString="16384" maxUrl="32768" /> </requestFiltering> </security> </system.webServer>