The request failed with HTTP status 413: Request Entirty Too Large error received when scanning in Web Client

replied on March 12, 2021

There is a limit in IIS that web client should already set high enough for it not to be a problem. In the file C:\Program Files\Laserfiche\Web Access\Web Files\web.config there should be something like:

<requestLimits maxAllowedContentLength="2097151000" maxQueryString="81920" maxUrl="81920" />

It's at line 176 in the current release, yours might be a little different. If you don't see it you can try adding it, but it needs to go into a particular place in the XML tree: https://stackoverflow.com/a/53428815. You can get an idea of how large the requests are by looking in the IIS logs for the requests that result in 413 error (C:\inetpub\logs\LogFiles\W3SVC1). The "cs-bytes" column should have that - cs means from client to server.

It's also possible that this isn't an error from the web client at all, there could be some kind of proxy in between. In that case, you would expect to not see the 413 error show up in the IIS logs.

0 0

replied on March 16, 2021

Thanks. So if the web client config file shows the correct maxAllowedContentLength and I'm not seeing a cs-bytes column in the log file you mentioned, then it's likely some other proxy in-between that's the cause?

0 0

replied on March 16, 2021

If you don't see the 413 error in the IIS log, then the request isn't reaching the web client machine. If that error is present, the cs-bytes column will tell you how large the request is, and you can compare that to what is in the web.config. If that column isn't present, you can modify your IIS logging to add it.

0 0

Question

Question

The request failed with HTTP status 413: Request Entirty Too Large error received when scanning in Web Client

Replies

Sign in to reply to this post.