Play 2.1.1 HTTP 413 trigger
See original GitHub issueHello.
I noticed that if you cross the 100kb default by a few bytes you’ll get a “HTTP/1.1 413 Request Entity Too Large” however, when i cross it with 105947(maybe this value is just for me) bytes i get a “HTTP/1.1 200 OK” again - which is bad since then all my validation returns false(because body is null).
I am assuming this is a bug?
Reproduce code:
public static Result test() {
Form form = Form.form.bindFromRequest();
ObjectNode result = Json.newObject();
// Return w/e the user sent as json
return ok(Json.toJson(form.get()));
}
Issue Analytics
- State:
- Created 10 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Play Framework 2.1.1 HTTP 413 trigger - Stack Overflow
I am having problems with Play! Framework 2.1.1. When sending a large(100kb+) request to my application (Play! 2.1.1) i get a "413 Request ......
Read more >Java Guide1 - 2.1.1 - Play Framework
In this tutorial you will learn the Play 2 Framework by coding a real web ... You can see the new application by...
Read more >Developing Web Services Applications Red Hat JBoss ...
Application and providing a custom implementation. 2.1.1. Simple Subclassing javax.ws.rs.core.Application. You can use ...
Read more >413 REDD PROJECT (413 PROJECT)
2.1.1 Summary Description of the Project (G1.2) . ... 5.5.2 Trigger Species Population Trends (GL3.2, GL3.3).
Read more >nginx-modules-reference-r20.pdf
2.7 Module ngx http auth request module . ... log level will cause all messages of the specified and more severe log ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe a clarification is in order. I don’t need a method to find out that body is too big. I want to be able to submit a form that has large body and process it on the server side - ideally without getting 413 screen of death.
There’s a config setting you can use: