Viktor
Oct 14, 2010
  7731
(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
Integrating Searchspring with Optimizely – Part 1: Architecture & Setup

Integrating Searchspring with Optimizely – Part 1: Architecture & Setup

Wiselin Jaya Jos | Mar 20, 2026 |

CMS 13 Preview 4 — Upgrading from Preview 3

This is the third post in a series where I use the Alloy template as a reference to walk through each CMS 13 preview. The first post covered...

Robert Svallin | Mar 20, 2026

The move to CMS 13: Upgrade Notes for Technical Teams

A technical walkthrough of CMS 13 preview3 and headless work: what is changing, where the risks are, and how an upgrade and what to expect

Hristo Bakalov | Mar 20, 2026 |

Customizing Product Data Sent to Optimizely Product Recommendations in Optimizely Commerce

A practical guide to customizing IEntryAttributeService in Optimizely Commerce so you can override product titles, add custom feed attributes, and...

Wojciech Seweryn | Mar 20, 2026 |