You can modify the element httpRuntime
in the archive web config. adding the following attribute. This should solve the problem of the object having null value when executing the POST.
// limite para o buffer de fluxo de entrada, em kilobytes
<httpRuntime maxRequestLength="2147483647" />
However, you may have problems with the requisition filtering introduced in IIS version 7.0. More specifically (my translation):
When request filtering blocks an HTTP request, IIS
7 will return an HTTP 404 error to the client and log HTTP status with
one substatus unique that identifies the reason why the request
was denied.
+----------------+------------------------------+
| HTTP Substatus | Descrição |
+----------------+------------------------------+
| 404.5 | Sequência URL Negada |
| 404.6 | Verbo Negado |
| 404.7 | Extensão de arquivo Negada |
| ... | |
To resolve this limitation, you can modify the element <requestLimits>
inside the archive web config.
// limita o POST para 10MB, query string para 256 chars, url para 1024 chars
<requestLimits maxQueryString="256" maxUrl="1024" maxAllowedContentLength="102400000" />
your API is being published by IIS?
– mercador
Yes, it’s being executed by the IIS
– Welber Silverio