413 Request entity too large in EP 7 (ESS)

[Former Member]

Hi

When users are trying to navigate within the portal (ESS) some users are getting 413 Request entry too large.

We found OSS note 657759 but since this only seems to affect some users we don't want to make this parameter change.

Could this have anything to do with auhtorisations?

Any help would be much appreciated.

Regards,

Caroline

Edited by: Caroline Didriksson on Mar 24, 2010 1:14 PM

[Former Member]

This was linked to profiles and authorisations.

[Former Member]

Hy Caroline,

we're facing the same problem with our ess portal - what do you mean exactly with profiles and authorizations?

kind regards

Thomas

SAP HELP:

Limiting the Length of the Request Body

Use

To protect your system from malicious denial-of-service attacks, you can set a limit on the request body length that can be accepted by the HTTP Provider Service on the Java dispatcher. The system controls this limit by inspecting the Content-Lengthheader of the request or monitoring the chunked request body (in case chunked encoding is applied to the message). If the value of the Content-Lengthheader exceeds the maximum request body length, then the HTTP Provider Service will reject the request with a 413 u201CRequest Entity Too Largeu201D error response.

You can limit the length of the request body using the MaxRequestContentLength property of the HTTP Provider Service running on the Java dispatcher. By default, the maximum permitted value is 131072 KB (or 128MB).

Procedure

You can configure the MaxRequestContentLength property using the Visual Administrator tool. Proceed as follows:

...

1. Go to the Properties tab of the HTTP Provider Service running on the dispatcher.

2. Choose MaxRequestContentLength property and enter a value in the Value field. The length is specified in KB.

3. Choose Update to add it to the list of properties.

4. To apply these changes, choose (Save Properties).

Edited by: Thomas Uhl on Nov 12, 2010 2:15 PM

[hofmann]

Thomas,

413 occurs when the browser is sending a HTTP Header that exceeds the specified size in VA. The HTTP Header is used to send data to the HTTP Server, like:

- User-Agent

- Referer

And the normally causing HTTP header parts:

- Cookie

- Authorization

When your solution is using cookies, make sure that the max length of the cookies does not exceed the MaxRequestContentLength. This can happen when you use custom cookies and store session information there.

Authorization: Negotiate occurs when the page requested requires authentication, and in the case of SPNego (Kerberos, Windows AD SSO) this value can get really huge when the user is attributed to a lot of AD groups (all groups in the AD are used to calculate the value).

br,

Tobias