B
Bram Kuijpers
Hi,
we have programmed a webservice, in VS 2003 /dotnet 1.1, and use it to
upload xml-files. The file is sent, as an attachment to a soap-file using
DIME, in one http-POST. The content can be larger than 4 Mb, which used to
give a http 500 error ("request too big" or something like that). So, I
changed the setting for maxRequestLength (to "10240") in web.config to fix
the problem. However, the result is now a http 400 (Invalid request) when
uploading a 5Mb file. I also tried changing maxRequestLength in
machine.config, but with the same result. We use Isapi Rewrite on the site
to translate URL's.
Does anyone have an idea about what causes the 400-code? Are there other
settings responsible for only processing 4Mb of a request?
Thanks,
Bram Kuijpers
we have programmed a webservice, in VS 2003 /dotnet 1.1, and use it to
upload xml-files. The file is sent, as an attachment to a soap-file using
DIME, in one http-POST. The content can be larger than 4 Mb, which used to
give a http 500 error ("request too big" or something like that). So, I
changed the setting for maxRequestLength (to "10240") in web.config to fix
the problem. However, the result is now a http 400 (Invalid request) when
uploading a 5Mb file. I also tried changing maxRequestLength in
machine.config, but with the same result. We use Isapi Rewrite on the site
to translate URL's.
Does anyone have an idea about what causes the 400-code? Are there other
settings responsible for only processing 4Mb of a request?
Thanks,
Bram Kuijpers