413 Request Entity Too Large Issue with Helicon redirect

[ramakantasahoo Profile]

Hi Team,

We are using Helicon to replace a header to something different but it seems due to this we get error Request Entity Too Large for header sizes of 5k+ .

</queryString>
<headersSize>5625</headersSize>
<bodySize>0</bodySize>
</request>
<response>
<status>413</status>
<statusText>Request Entity Too Large</statusText>
<httpVersion>HTTP/1.1</httpVersion>
<cookies/>
<headers>
<header>
<name>Content-Type</name>
<value>text/html</value>
</header>
<header>
<name>Server</name>
<value>Microsoft-IIS/8.5</value>
</header>
<header>
<name>Persistent-Auth</name>
<value>true</value>
</header>
<header>
<name>X-Powered-By</name>
<value>ASP.NET</value>
</header>
<header>
<name>Date</name>
<value>Wed, 23 Nov 2016 17:13:08 GMT</value>
</header>
<header>
<name>Content-Length</name>
<value>67</value>
</header>
</headers>
<content>
<size>67</size>
<mimeType>text/html</mimeType>
<text>The page was not displayed because the request entity is too large.</text>
</content>
<redirectionURL/>
<headersSize>196</headersSize>
<bodySize>67</bodySize>
</response>
<cache/>
<timings>
<send>15</send>
<wait>234</wait>
<receive>0</receive>
</timings>
</entry>

Not sure if this is directly related to but we have tried all changes like bumping up the settings i.e max_packet_size, uploadReadAheadSize, Maximum query string and max url length, MaxRequestBytes, Maximum allowed content length, etc.

We are not able to reproduce the issue if we uninstall helicon and keeping IIS default settings.

Helicon config:

RewriteEngine on
RewriteCond %{REMOTE_USER} (.*)\\(.*)
RewriteHeader SSOUSER: .* (%2)(@)(%1)(.com)
RewriteHeader Authorization: .* ()


IIS is 8.5 on windows 2012 R2 with HTTPS enabled.


Please help incase we have some settings in helicon side to fix the issue. Thanks

[Yaroslav]

Hello.

I'm not sure if this is something that is possible to fix. There is no strict limitation on header length anywhere in ISAPI_Rewrite code so I suppose this limitation bumps because of some limitation in IIS API itself. Anyway, having a header of 5k+ size may hint to a badly designed application. HTTP headers were not intended to be used for large data transfer. Maybe you could consider changing the application behavior or at least explain why you need an HTTP header of such size?