Here is the setup: migrating a page that takes an encrypted string from a query string and processes it to redirect to the wanted page.
The problem: The querystring is too long (8760) and the result goes to a page not found but if I truncate the encrypted string it to a much shorter length (2035 or less), it goes through, but of course it does not process)
More info: I have so far added in the keys
<httpRuntime targetFramework="4.6.1" maxRequestLength="2097151" waitChangeNotification="1" maxWaitChangeNotification="3600" requestValidationMode="2.0" maxQueryStringLength="32768" maxUrlLength="65536" enable="true"/>
I am at a loss, and can only think there is some sort of hidden setting that I am missing but cannot figure it out.
The sample URL I am useing (to give you an idea of the length is:
http://localhost:1112/SSO/Consume?SAMLResponse=<samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified" Destination="https://welltok.quitlogix.org/SSO/Consume.aspx" ID="_d69e098f3cd331ddcc40e66da31900a2" IssueInstant="2020-10-22T23:59:40Z" Version="2.0"><Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">https://cafewell.com</Issuer><samlp:Status><samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/></samlp:Status><saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="_5b93ae47d3bc2ab4d469b135eb814f51" IssueInstant="2020-10-22T23:59:40Z" Version="2.0"><saml:Issuer>https://cafewell.com</saml:Issuer><ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:SignedInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></ds:CanonicalizationMethod><ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></ds:SignatureMethod><ds:Reference URI="#_5b93ae47d3bc2ab4d469b135eb814f51"><ds:Transforms><ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></ds:Transform><ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></ds:Transform></ds:Transforms><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod><ds:DigestValue>kMQgRjtxL6jUGk7shDbw1An0VQM=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>XFI0qdJ3UYzBKEDLTvcuWn8Brq3cr3sJyOyAdfl7by+B+Jsv9ZXy4ECKHiIUIUv+dIDqph3Csz59GPpVgzGMrcU4QebigbXLVovNCTAV5tYVAb6NyRlZyqojFWwtFLtXjS6okVfa1dzRRIvFJrSN5XA/9YSMMtZBXlJUBzZXhGUuYr8VI4hwijAijT47sBoVnO9okZ5Bvqv+1vYhUFdBH6KOhG4wIHmq08Z+I6w/Ewguv18XvOimHbvI/Y5w6BSoJ06yzpfqGIWVfw1PgN3ptbidObpgHwEmKJj4WeVOY8d0RN1k3z2NKB+jC1fjFoOxEwaPA9awE4D3bJg5QvZHdsA0pVaKk4182P+HFGArQGXeW/6ski5GUXXskNMqTL6gdob5f+xuhsucNlvN9mOvsGSEGyKW6wSpPVBkBJ8HN8eftkaADUP8RVhgEgzfzybltQ6Uj0FQm/pfBEWQPDiyvnHknBEYZoa9L6oFvS/iMADWJ3MfN40ux5EBIWfujxg8Af8cb/jHJnq1yKROCFW3gk8cZ6gEk6MgWrH5XH+EZlzb6tbnJtFS9WHkQbsZBvJWG8kIA09C9OqsRgAzenoiT+I4SE/MDApTMpM/DBHNnj5VXxTt/55WW2AkTYMaYd0rF74Sol4BeJF/Fe/gLvo01pKX3xSpSRZam7IEcGJC6OQ=</ds:SignatureValue><KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"><ds:X509Data><ds:X509Certificate>MIIIZzCCB0+gAwIBAgIQC80KddLwC/UDK+ehukhYCjANBgkqhkiG9w0BAQsFADBwMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMS8wLQYDVQQDEyZEaWdpQ2VydCBTSEEyIEhpZ2ggQXNzdXJhbmNlIFNlcnZlciBDQTAeFw0yMDAzMDQwMDAwMDBaFw0yMjA2MDcwMDAwMDBaMGIxCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMRYwFAYDVQQKEw1XZWxsdG9rLCBJbmMuMRcwFQYDVQQDDA4qLmNhZmV3ZWxsLmNvbTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBAMGHZr9+9GL9W/Yb4h/a48bLQOJW4rHZIr8GaUpDVZlKkKiZxw/UfUQW5DSdSHSXdZaTUgLTz06zHskRGwIwqnD5zx3HcOV2EWaD+HLaaN4A2BUSBGC0dR7Idx6yqEyztag7Ky6LXR6UjlrjJ0842eUSnwF+NsVqcAHn232e8fD6z4A1p7j8OSdFlb8Bfv1fEX3xT0dcABgkgJ+/VsvnzjvOZfQA+q/POeZp5cwLMDwgZYkb5AHmBq0EWPtvFkGr/b5mKuuoqLfy9smTv4rvJRtt2N1nQE6zvyK29sULzKLsdA9hHocI+VbjNk4Otq30RzMLyCv+G8Wes+WNHVDrmU9ZfME4I1B70J+JRhCxT8Y+o/+IYTyUuaIxcWdKiHSJYQDi9kE92tfaYVmYh9FOWQJBNIrDS0UutpY/samq/0p37lxpJJFQyrpioyR0sSD/AjiyGKzBHzQAkvOEGhMhm0mP2Vk76PHYZjG+5L3dPYSPqtFbq9l28u+gql/V3Ww4URlAnsG/FGp8AV+KCNnUdmTKcK8AClfNmEv4SMnR/xat7Wh5mQG6ksCPEIfLQWGw0AHOfPNAwIYRDSlOZs43+M9VMm1Wzw30V4REn7lcXjmhMuyJnyWYmskEJ0AAt/EEtktcB0FTxmwnOULNRDacFjCXMydqYSi6AHOz8bQfTqLHAgMBAAGjggQJMIIEBTAfBgNVHSMEGDAWgBRRaP+QrwIHdTzM2WVkYqISuFlyOzAdBgNVHQ4EFgQUCt+rE2lrLxYSJTCfVFAT4GeCrJIwPwYDVR0RBDgwNoIOKi5jYWZld2VsbC5jb22CDGNhZmV3ZWxsLmNvbYIWZGVpcy1wcm9kLmNhZmV3ZWxsLmNvbTAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMHUGA1UdHwRuMGwwNKAyoDCGLmh0dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9zaGEyLWhhLXNlcnZlci1nNi5jcmwwNKAyoDCGLmh0dHA6Ly9jcmw0LmRpZ2ljZXJ0LmNvbS9zaGEyLWhhLXNlcnZlci1nNi5jcmwwTAYDVR0gBEUwQzA3BglghkgBhv1sAQEwKjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzAIBgZngQwBAgIwgYMGCCsGAQUFBwEBBHcwdTAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tME0GCCsGAQUFBzAChkFodHRwOi8vY2FjZXJ0cy5kaWdpY2VydC5jb20vRGlnaUNlcnRTSEEySGlnaEFzc3VyYW5jZVNlcnZlckNBLmNydDAMBgNVHRMBAf8EAjAAMIIB+AYKKwYBBAHWeQIEAgSCAegEggHkAeIAdwApeb7wnjk5IfBWc59jpXflvld9nGAK+PlNXSZcJV3HhAAAAXCmG+acAAAEAwBIMEYCIQCIKELaKsYE0LIyyYKekA6mxGv9Qdg+NXsFrJwRObULZQIhANZFhzGMEojUvvh9m+aI1DfEoD+flAebA4OzMx/1xhn8AHYAIkVFB1lVJFaWP6Ev8fdthuAjJmOtwEt/XcaDXG7iDwIAAAFwphvm9wAABAMARzBFAiAYcLYZDdz3LML/TDsJbsPyH1FSUlNVvXI8jUVGet5qGwIhAIWSlbRHUvJ0EMjy9RS2BAlYR8UljZBHpdmwvrWS/nAVAHcApLkJkLQYWBSHuxOizGdwCjw1mAT5G9+443fNDsgN3BAAAAFwphvmngAABAMASDBGAiEAyQJt8KFkJJe8GrWsFQWjjMz5hZO2C3v2iBE7V4VMnOoCIQCbvjH3hn8cdvrr6IslNWNhiCyKzGc/Smvf9rrM2wHlSgB2AEHIyrHfIkZKEMahOglCh15OMYsbA+vrS8do8JBilgb2AAABcKYb5psAAAQDAEcwRQIhAMfawOiaB4cbNEFcePNiEm4W0ivhxevSKP0xps9jKgE3AiB5kKlP51wtVbDUlghlJ5ZGzalbRwqyRrZVHAfi3/8UKTANBgkqhkiG9w0BAQsFAAOCAQEAXC2RhT2nv5UDCvXrXM255FNb6J1b3F46e1mxnHC4SLq6o/5aeXa2joKJj+FsJSZggIBBE7/ZjUjgs1nqqKNzJS9qQbhD7fp+XDz0WkqC7CveNd9CjwpxRaClEG6SvzyMqiKh1eDYzr6e+zeaVAIPypz8tZpcA2JwP7uKap930zXsEdiFjWHD/E8vUAA/Zbv+4y7cOARpRNNMNNehOE0ei1PaoRXQOraPPU8ZW/zJZBEit9Refw0StS14YpS7QdG3nhlgpC8eKXV9w1Or2iSUd/d+HqYnAUfCXCixHLI0buAvwzyWF6v6xiyjWlpviJJ0vb+sbNqzjoZqnuApp8eJ8A==</ds:X509Certificate></ds:X509Data></KeyInfo></ds:Signature><saml:Subject><saml:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">0f0226a3-abc7-4c62-942b-f107c04f792d</saml:NameID><saml:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer"><saml:SubjectConfirmationData NotOnOrAfter="2020-10-23T00:02:40Z" Recipient="https://welltok.quitlogix.org/SSO/Consume.aspx"></saml:SubjectConfirmationData></saml:SubjectConfirmation></saml:Subject><saml:Conditions NotBefore="2020-10-22T23:59:35Z" NotOnOrAfter="2020-10-23T00:59:40Z"><saml:AudienceRestriction><saml:Audience></saml:Audience></saml:AudienceRestriction></saml:Conditions><saml:AttributeStatement><saml:Attribute Name="UUID"><saml:AttributeValue>0f0226a3-abc7-4c62-942b-f107c04f792d</saml:AttributeValue></saml:Attribute><saml:Attribute Name="RelayState"><saml:AttributeValue>/quit/goals.aspx</saml:AttributeValue></saml:Attribute><saml:Attribute Name="username"><saml:AttributeValue>1000052_e</saml:AttributeValue></saml:Attribute><saml:Attribute Name="task"><saml:AttributeValue>33716b52-3722-41d7-8a1e-d79bd9b1d5c6</saml:AttributeValue></saml:Attribute></saml:AttributeStatement><saml:AuthnStatement AuthnInstant="2020-10-22T23:59:40Z" SessionIndex="_5b93ae47d3bc2ab4d469b135eb814f51"><saml:AuthnContext><saml:AuthnContextClassRef>urn:federation:authentication:windows</saml:AuthnContextClassRef></saml:AuthnContext></saml:AuthnStatement></saml:Assertion></samlp:Response>
What browser are you using to test? IE11 has URL length limitations that are shorter than what IIS can handle.
In the tests in the link above, IE11 was able to handle up to "4043" characters in the URL.
It also appears there are 2 places where your update might need to be made.
<configuration>
...
<system.webServer>
...
<security>
<requestFiltering>
<requestLimits maxQueryString="8192" />
</requestFiltering>
</security>
</system.webServer>
</configuration>
and
<configuration>
...
<system.web>
...
<httpRuntime ... maxQueryStringLength="8192" />
</system.web>
</configuration>
In situations where a large amount of data needs sent to an application, like in a SAML request, the request is made as a POST with the data in the request body, rather than as a GET, so they are not subject to URL length limitations.
I also don't think this issue is a Kentico problem, unless you are seeing different results in a new WebForms application project with the same web.config settings.
Related
I have an ASP.NET site that is calling a service. It can take the service several minutes to produce the response back in some cases and I am seeing the "Thread was being aborted" exception in those cases.
Is this related to a timeout setting somewhere? Can the timeout be increased?
Update:
Once I have increased the timeout as suggested by Brando Zhang, I am not seeing the "Thread was being aborted" exception, but the page itself is timing out for some reason. By "timing out" I mean that the page is not being refreshed with the contents of the response, once it arrives.
Now my Web.config has the following setting:
<configuration>
<system.web>
<httpRuntime executionTimeout="360" />
</system.web>
</configuration>
Update 2:
Since the original problem outlined in the title is in fact resolved, I feel that the answer provided by Brando Zhang can be accepted as a valid answer to this question.
I will try to resolve the new issue mentioned in the first update by reducing the time it takes for the request to complete or by using long polling.
According to your description, I suggest you could try to increase the executionTimeout property to avoid the thread aborted exception.
Details, you could refer to below config setting:
<configuration> <system.web>
<httpRuntime executionTimeout="360" />
</system.web>
</configuration>
I could not find the specific answer to this when searching so I'm posting my solution here.
We were working fine with SignalR for a long time, then some users started getting 404 errors on the start and connect calls from AngularJs/jQuery to the server. Negotiate would work fine though and return a 200 code.
It turns out by default the server side (ASP.NET 4.6.1) must impose a limit on the size of a URL and instead of returning a 414 (Request-URI Too Long) like you might expect it must just truncate the URL at a length around 2,083 and still try to process it. I'm assuming the 404 is the SignalR hub responding because now the truncated string has query string parameters that don't match what is expected. We were seeing it because we were passing a couple custom values and the security access token via query string parameters which increased the size. The access token was passed via query string because we wanted to use websockets and headers don't exist for websockets. As you add more attributes and roles to your token it will grow which is what put us over the default size limit.
The fix is easy. Just update your server web.config to allow longer URLs.
<system.web>
<httpRuntime targetFramework="4.5" maxRequestLength="30000000" maxUrlLength="40960" maxQueryStringLength="2097151" />
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="30000000" maxUrl="40960" maxQueryString="2097151" />
</requestFiltering>
</security>
</system.webServer>
I have a service written using servicestack v3.9. I am trying to return a large result set and am getting an 500 internal server error on my client. If I look at the details of the error I see the results are listed in the exception but are truncated after 65536 characters. I know this is a default limit imposed by .net. What I don't know is how to increase it for service stack.
My client isn't connecting to the service using a binding in the web config since it's using service stack. For web api calls this seems like where you would fix this issue be increasing maxReceivedMessageSize in the binding. I am guessing there is some way to increase this limit for service stack too??
ServiceStack doesn't impose any limits or quota's itself, so any limits your Services hit are IIS/ASP.NET's which can be increased the same as any other ASP.NET Web Application.
The Web.Config example configuration below shows how to increase the request limit to 1GB in both IIS6 and IIS7:
<configuration>
<system.web>
<httpRuntime maxRequestLength="1048576" />
</system.web>
</configuration>
For IIS7 and above, you also need to add the lines below:
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="1073741824" />
</requestFiltering>
</security>
</system.webServer>
I encountered a weird case during debugging a WebAPI controller for saving files.
My controller has a method for posting data
[HttpPost]
[HttpPut]
public async Task<HttpResponseMessage> Upload()
{
if (!request.Content.IsMimeMultipartContent())
{
throw new HttpResponseException(HttpStatusCode.UnsupportedMediaType);
}
var provider = await request.Content.ReadAsMultipartAsync();
MultipartFileData file = provider.FileData.FirstOrDefault();
// this is the uploaded file: file.LocalFileName
}
Controller's logic doesn't matter much here. The key point here is that the controller expects multipart-content.
Now from the client where I'm using jquery.fileupload library I send files via POST method.
I set a breakpoint on the first line of the controller's Upload method and send a file from the client. The breakpoint goes off. It goes off before all file were uploaded to the server. It's expected behavior and everything is good.
Now the problem. I send a large file and the breakpoint doesn't go off. The file is being uploaded (POSTed) and the controller isn't being called!
Event worse that after the file is finally uploaded I get 404 Not Found on the client.
My site is on localhost under IIS with ASP.NET Web API 5.1.2 (.NET 4.5).
I start changing file size to choose the size when the things works. It turns out that is't 1000000000 (one million bytes). If a request's length (data and headers) is 1M bytes that everything works: breakpoint goes off and the file is uploaded. If a request's length 1 byte more that nothing works: breakpoint doesn't go off, the file seems to being uploaded (i.e. tha data is sending) but it's unclear where it's uploaded as the controller isn't called.
As my site on localhost I can't believe it's caused by proxy server.
So my question is what is going on? What can be wrong with posting 1M bytes requests?
p.s. I'm aware of IIS and ASP.NET hard limits for request lengths (4Gb and 2Gb) - they are not exceeded.
In IIS Manager click on your site and go Configuration Editor - you will need to alter maxRequestLength to a value that will work with your requirements.
Edit:
The second place request limits are set are here:
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="1000000000" /> <!-- change this -->
</requestFiltering>
</security>
</system.webServer>
So I completely forgot about settings in web.config. It turns out that 1M was the limit set there :(
<system.web>
<httpRuntime maxRequestLength="1000000000" />
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="1000000000" />
</requestFiltering>
</security>
</system.webServer>
I have a WCF service (over a webHttpBinding) using ASP.NET 4/IIS 8 and I had no problems communicating with it using JSON with GET. However, today I needed to implement a method that sends a large query string (about 3000 characters, not that long but longer than that I've been using). I called the service and immediately got a 404 error, without even stepping into my code at my debug machine. The first thing that came to my mind is the maximum query string length limit. I've added this to my web.config:
<system.webServer>
<directoryBrowse enabled="true" />
<security>
<requestFiltering>
<requestLimits maxQueryString="8000"></requestLimits>
</requestFiltering>
</security>
</system.webServer>
Now, I am getting this server error when I call the service: The length of the query string for this request exceeds the configured maxQueryStringLength value. Weird enough, I've tried other values such as 200000, way over my query string and URL, which is about 3000 characters. Am I missing something?
Maybe set maxQueryStringLength in the httpRuntime element.
It's a bit confusing to have two configuration settings, but I believe they can be interpreted as follows:
The httpRuntime maxQueryStringLength property is new to ASP.NET 4 and configures the maximum query string length that can be processed by the ASP.NET HTTP runtime. Prior to ASP.NET 4 this was a hardwired value of 2048; it can now be increased.
The system.web/security/requestFiltering maxQueryStringLength property is an IIS 7 setting and allows an administrator to restrict the maximum query string length. This setting isn't specific to ASP.NET.