Viktor
Oct 14, 2010
  7837
(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
Optimizely Developers The Netherlands Meetup 2026

  I'm excited to not only co-host the upcoming  Optimizely Developers (The Netherlands) Meetup on my home turf at iO  in Den Bosch with Ehsan Ahzar...

WilliamP | Jun 5, 2026

Automatic assign of content reference properties on content creation

A long time ago I was tired of configuring setting properties on a settings page when deploying new functionality that needed global settings, so I...

Per Nergård (MVP) | Jun 5, 2026

Optimizely Opal vs AI-Assistant

This page compares strengths, use cases, flexibility, and pricing—highlighting Opal’s breadth vs Epicweb’s depth and how they can complement each...

Luc Gosso (MVP) | Jun 2, 2026 |

Optimizely PaaS CMS Administrator Certification (2025): What to Expect and How to Prepare

The Optimizely PaaS CMS Administrator certification is best understood as training for the operational side of Optimizely CMS. It focuses on how th...

Augusto Davalos | Jun 2, 2026