Viktor
Oct 14, 2010
  7744
(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
Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |