Bad Request - Invalid URL (v2021)

lfernandes · Post by **lfernandes** » Fri Jan 07, 2022 6:34 am

We are using File Upload to Folder. However, we found that the download links for files generated by ASPNETMAKER have shown an error, Bad Request - Invalid URL
HTTP Error 400. The request URL is invalid. Apparently this error occurs for files with names longer than 100 characters and/or that have many special character references.

Are there any limitations for this feature? How to solve ?

It is noteworthy that when we rename the files the code generated by ASPNETMAKER works normally.

MichaelG · Post by **MichaelG** » Fri Jan 07, 2022 6:52 am

Please make sure that you are using utf-8 project (HTML -> Charset = "utf-8") and the file name consists of utf-8 characters. Alternatively, show a problem file name.

lfernandes · Post by **lfernandes** » Fri Jan 07, 2022 7:00 am

yes, we are using utf-8 project (HTML -> Charset = "utf-8"). Example of the filename causing the error:
CONTRATO PARCERIA POLO SÃƒO JOÃƒO DA PONTE-MG_Ctt_Parceria_SÃƒO JOÃƒO DA PONTE - MG_YDUQS - SANTA_CATARINA_.pdf

MichaelG · Post by **MichaelG** » Sat Jan 08, 2022 6:20 am

You may need to increase the maxAllowedContentLength / maxUrl / maxQueryString in web.config. For example:

	<security>
		<requestFiltering>
			<requestLimits maxAllowedContentLength="..." maxUrl="..." maxQueryString="..." />
		</requestFiltering>
	</security>

lfernandes · Post by **lfernandes** » Tue Jan 11, 2022 11:06 pm

In ASPNETMAKER in tools - advanced settings - option "encrypt file path" when disabling and regenerating the project the file url works.

So I conclude that the problem is related to the file path encryption functionality.

In which part of the ASPNETMAKER code can we check the logic of this functionality?

MichaelG · Post by **MichaelG** » Wed Jan 12, 2022 5:58 am

With encrypted file path, the URL will become a very long string, so that still points to the same problem per my previous reply .

You may need to increase the maxAllowedContentLength / maxUrl / maxQueryString in web.config.

lfernandes · Post by **lfernandes** » Fri Jan 14, 2022 1:28 am

The suggested solution did not solve the problem

MichaelG · Post by **MichaelG** » Fri Jan 14, 2022 5:49 am

Show your changes.

lfernandes · Post by **lfernandes** » Tue Jan 18, 2022 10:55 pm

Michael,
the problem was worked around by applying the following configuration in the web config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>

<system.web>
<httpRuntime maxQueryStringLength="32768" maxUrlLength="65536" />
</system.web>
<system.webServer>
<handlers>
<add name="aspNetCore" path="" verb="" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\AspNetMaker2021.dll" requestTimeout="00:02:00" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess"></aspNetCore>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="52428800" maxQueryString="32768" maxUrl="65536" />
</requestFiltering>
</security>
</system.webServer>

darkdragon · Post by **darkdragon** » Wed Jan 19, 2022 2:38 am

If you use IIS, there is a limit from http.sys
Check the docs: https://docs.microsoft.com/en-us/troubl ... ry-windows