Viktor
Oct 14, 2010
  7852
(2 votes)

Querystring too long in EPiServer Composer

Stumbled upon an issue with EPiServer Composer 4 and that the query string was too long. Not entirely sure how great this fix is out of a security stand point, but if anyone else knows a better solution please let me know.

The error
HTTP Error 404.15 - Not Found
The request filtering module is configured to deny a request where the query string is too long.

The solution

    <system.webServer>
        <security>
            <requestFiltering>
                <requestLimits maxQueryString="2097151" />
            </requestFiltering>
        </security>
</system.webServer>
Oct 14, 2010

Comments

May 15, 2012 01:06 PM

I'm using W2008 and IIS 7.5, and experied problems when trying to edit a layout block containing several other layoutblocks containing contentblocks. The generated querystring was insanely huge.

I solved it by adding a requestLimits tag under the location path "dropit/plugin/extension/ui/edit".















Please login to comment.
Latest blogs
CI/CD deployment failure in Optimizely DXP Passportal. .NET 10 and GitHub Runner Compatibility

.NET 10 and GitHub Runner Compatibility With the release of .NET 10, the windows-latest and ubuntu-latest GitHub Actions runners may use the latest...

owaiskhan | Jun 16, 2026

Integrating Optimizely CMP Assets into an Existing Document Listing Page

Integrating Optimizely CMP Assets into an Existing Document Listing Page In some projects, there may be a requirement to retrieve assets from...

owaiskhan | Jun 16, 2026

Setting up Opti Id SSO with and without SCIM

This blog compiled learnings, when setting up Opti Id for large enterprises using SCIM and its pros and cons when setting up Opti Id without SCIM....

Muhammad Talha | Jun 16, 2026

Understanding Optimizely Opal Cost vs Value

Every Opal conversation seems to start with the same question: "What does it cost?" Fair, but it's only half the question. Cost tells you what you'...

K Khan | Jun 15, 2026