HTTP Error 413.1 - Request Entity Too Large

The page was not displayed because the request entity is too large.

Most likely causes:

  • The Web server is refusing to service the request because the request entity is too large.
  • The Web server cannot service the request because it is trying to negotiate a client certificate but the request entity is too large.
  • The request URL or the physical mapping to the URL (i.e., the physical file system path to the URL's content) is too long.

Things you can try:

  • Verify that the request is valid.
  • If using client certificates, try:
    • Increasing system.webServer/serverRuntime@uploadReadAheadSize
    • Configure your SSL endpoint to negotiate client certificates as part of the initial SSL handshake. (netsh http add sslcert ... clientcertnegotiation=enable)

Detailed Error Information:

Module   RequestFilteringModule
Notification   BeginRequest
Handler   ExtensionlessUrlHandler-Integrated-4.0
Error Code   0x00000000
Requested URL   https://lfweb.city.salem.int:443/ldps/api/v1/document/token
Physical Path   C:\Program Files\Laserfiche\Document Preview\api\v1\document\token
Logon Method   Not yet determined
Logon User   Not yet determined

More Information:

This error occurs when the Web server receives a large amount of data from the client. It also occurs if client certificate negotiation occurs while receiving a large request.

View more information »

OperationID: 0000730867d36df763d3d9e683a989db Operation: /laserfiche/DocumentService.ashx/GetMetisToken Message: Exception details: Message: IIS 10.0 Detailed Error - 413.1 - Request Entity Too Large

HTTP Error 413.1 - Request Entity Too Large

The page was not displayed because the request entity is too large.

Most likely causes:

  • The Web server is refusing to service the request because the request entity is too large.
  • The Web server cannot service the request because it is trying to negotiate a client certificate but the request entity is too large.
  • The request URL or the physical mapping to the URL (i.e., the physical file system path to the URL's content) is too long.

Things you can try:

  • Verify that the request is valid.
  • If using client certificates, try:
    • Increasing system.webServer/serverRuntime@uploadReadAheadSize
    • Configure your SSL endpoint to negotiate client certificates as part of the initial SSL handshake. (netsh http add sslcert ... clientcertnegotiation=enable)

Detailed Error Information:

Module   RequestFilteringModule
Notification   BeginRequest
Handler   ExtensionlessUrlHandler-Integrated-4.0
Error Code   0x00000000
Requested URL   https://lfweb.city.salem.int:443/ldps/api/v1/document/token
Physical Path   C:\Program Files\Laserfiche\Document Preview\api\v1\document\token
Logon Method   Not yet determined
Logon User   Not yet determined

More Information:

This error occurs when the Web server receives a large amount of data from the client. It also occurs if client certificate negotiation occurs while receiving a large request.

View more information »

Stack trace: Exception encountered, stack trace: WebAccessServices.HttpHandlers.d__86.MoveNext System.Threading.ExecutionContext.RunInternal System.Threading.ExecutionContext.Run System.Runtime.CompilerServices.MoveNextRunner.Run System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction System.Threading.Tasks.Task.FinishContinuations Repository: Revenue Session: uog2nh3y