Viktor
Oct 14, 2010
visibility 7922
star star star star star
(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".















error Please login to comment.
Latest blogs
Parallel Development in Optimizely CMS SaaS: Shifting to a Schema Migration Mindset

  Part 3 of the Parallel Development series. The branch-scoped push script from Part 1 works. Run it on a feature branch where you've touched a...

Vipin Banka | Jul 25, 2026

From AI Agents to AI Workflow with Opal

Introduction In the first article in this series , we talked about AI agents in Optimizely Opal and walked through the process of creating a...

Igor Safonov | Jul 23, 2026

Building Your First Optimizely Opal AI Agent: a Hands-On Walkthrough

Introduction There's a common assumption that building an AI agent is something only engineers or developers can do. It isn't. At the Optimizely AN...

Igor Safonov | Jul 23, 2026

Advanced Task Manager Gets a Big Update

One of the things I keep coming back to with Optimizely's content approval workflow is that it's solid at the individual level - you know a piece o...

Adnan Zameer | Jul 21, 2026 |