My Oracle Support Banner

HTTP Server Returns HTTP-413 Request Entity Too Large Despite No Such Limit Is Hit (Doc ID 400125.1)

Last updated on JUNE 29, 2023

Applies to:

Oracle HTTP Server - Version 10.1.2.0.2 to 10.1.3.4.0 [Release AS10gR2 to AS10gR3]
Oracle Containers for J2EE - Version 10.1.2.0.2 to 10.1.3.4.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.
Oracle Containers for J2EE - Version: 10.1.2.0.2 to 10.1.3.4.0
This problem can occur on any platform.
 

Symptoms

A rich client sends a POST request (XMLRPC) via the HTTP Server and mod_oc4j to a J2EE application in OC4J.

The POST request has jsessionid encoded in the URL, and there is are to directly-following slashes in the URL, i.e. the request like looks like:

Despite the POST body and request Content-Length is small (<4KB) and there are no configured limits for any of LimitRequestBody, LimitRequestFields, LimitRequestFieldsize and LimitRequestLine.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.