Re: cloud foundry - 413 Request Entity Too Large


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

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.