title: request exceeds the configured maxQueryStringLength when using [Authorize]
body: <p><img src="https://i.stack.imgur.com/aJHgW.png" alt="enter image description here"><br>
  I have a MVC3 site in C#, I have a particular view being fed query parameters from a JavaScript function, the function redirects to the site via </p>
  
  <blockquote>
    <p>window.location.href = "../ActionName?" + query_string;</p>
  </blockquote>
  
  <p>query_string being the dynamic query parameters string built by the JavaScript function.</p>
  
  <p>The reason for this weirdness is that sometimes the same function passes the URL to an ASP.Net webform due to it having to use the <strong>reportviewer</strong> control, the alternate action is to save some parameters in this case it passes to the view. (Can elaborate more if that does not make sense)</p>
  
  <p>The whole thing works fine until I introduce [Authorize] to the action method.
  Breaks if it is in place, works fine without, and [Authorize] works fine on all the other methods.</p>
  
  <p>The whole URL in this case is 966 chars long, after research it seems that the <strong>maxQueryStringLength</strong> value is 2048 by default but can overridden to any value of type integer, so just for grins I added the </p>
  
  <pre><code>&lt;security&gt;
    &lt;requestFiltering&gt;
      &lt;requestLimits maxQueryString="2048"&gt;&lt;/requestLimits&gt;
    &lt;/requestFiltering&gt;
  &lt;/security&gt;
  </code></pre>
  
  <p>key to the web config file under the   key.</p>
  
  <p>No joy there, so I got ridiculous and made it 4096, still no joy.</p>
  
  <p>Now with the whole URL being 966 chars long, the authorize attribute cannot seriously be adding another 1082-3130 chars, so how can I determine what the error actually is, or why the setting is not taking effect.</p>
  
  <p>VS2010 Pro SP1</p>