cloud foundry - 413 Request Entity Too Large


avia <Avia.Ohana@...>
 

Hello,

I'm using Cloud Foundry v2, pivotal v1.4 distribution.
All my apps are written in java, build pack is java_buildpack_offline_v3.0.

Trying to make REST call with ~12MB body size to one of my apps, and getting error 413 Request Entity Too Large with the following headers:
X-Cf-Requestid c80a7e06-7102-459e-721a-251189596ece
Date Sun, 07 Jun 2015 08:20:45 GMT
Content-Length 0
Content-Type text/plain; charset=utf-8

What is the default body size limit in cloud foundry? How can I configure it?
Any idea?

Thanks in advanced,
Avia


James Bayer
 

since this is commercial software you can always open a support case with
pivotal to get help with an SLA.

cf doesn't limit the body size, but i think the max upload size is
somewhere around 1GB or so. is the 413 error code coming from tomcat or
some other middleware? what kind of app do you have and how is it packaged?
do you have any of the logs to share? what kind of REST call, is it a GET
with large headers, a POST or PUT?

On Tue, Jun 9, 2015 at 10:04 AM, Ohana, Avia <Avia.Ohana(a)emc.com> wrote:

Hello,



I'm using Cloud Foundry v2, pivotal v1.4 distribution.

All my apps are written in java, build pack is java_buildpack_offline_v3.0.



Trying to make REST call with ~12MB body size to one of my apps, and
getting error 413 Request Entity Too Large with the following headers:

X-Cf-Requestid c80a7e06-7102-459e-721a-251189596ece

Date Sun, 07 Jun 2015 08:20:45 GMT

Content-Length 0

Content-Type text/plain; charset=utf-8



What is the default body size limit in cloud foundry? How can I configure
it?

Any idea?



Thanks in advanced,

Avia

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer


avia <Avia.Ohana@...>
 

Hi James,

The 413 error doesn't come from our app. Our app doesn't get the POST
request with body size >= ~12MB.

We are using netty jax-rs.
All I can see in app logs is:
2015-06-15T14:28:55.000+00:00 [RTR] OUT
listenerendpoint.appscf.wysdm.lab.emc.com:80 - [15/06/2015:14:28:55 +0000]
"POST /listener-endpoint-api/agent/nbustomaster/report HTTP/1.1" 413 0 "-"
"Apache-HttpClient/4.2.1 (java 1.5)" 10.98.61.131:53703
x_forwarded_for:"10.98.63.219, 10.98.61.131"
vcap_request_id:4508262e-26e9-4837-4f08-505b65863fec
response_time:0.304191621 app_id:582630d6-de94-41b9-a539-0e3a4fad1725

any idea?



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-cloud-foundry-413-Request-Entity-Too-Large-tp350p425.html
Sent from the CF Dev mailing list archive at Nabble.com.


James Bayer
 

are you sure that the request isn't making it all the way to the app
container?

are there features of netty that you can log the request as it's coming in
with lots of logging for different aspects of the request lifecycle? e.g.
tcp connection established, etc.

On Mon, Jun 15, 2015 at 7:47 AM, avia <Avia.Ohana(a)emc.com> wrote:

Hi James,

The 413 error doesn't come from our app. Our app doesn't get the POST
request with body size >= ~12MB.

We are using netty jax-rs.
All I can see in app logs is:
2015-06-15T14:28:55.000+00:00 [RTR] OUT
listenerendpoint.appscf.wysdm.lab.emc.com:80 - [15/06/2015:14:28:55 +0000]
"POST /listener-endpoint-api/agent/nbustomaster/report HTTP/1.1" 413 0 "-"
"Apache-HttpClient/4.2.1 (java 1.5)" 10.98.61.131:53703
x_forwarded_for:"10.98.63.219, 10.98.61.131"
vcap_request_id:4508262e-26e9-4837-4f08-505b65863fec
response_time:0.304191621 app_id:582630d6-de94-41b9-a539-0e3a4fad1725

any idea?



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/cf-dev-cloud-foundry-413-Request-Entity-Too-Large-tp350p425.html
Sent from the CF Dev mailing list archive at Nabble.com.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
--
Thank you,

James Bayer