What is the downside to setting large value or disabling the maxPostSize and maxSavePostSize limitations in JBoss EAP/JBossWeb/Tomcat?
Issue
- We have a requirement to have a higher POST size than the 2M limit. What is the downside of setting this to large value or -1 (unlimited) to
maxPostSizeandmaxSavePostSizein EAP 4.x/5.x? - We have a requirement to have a higher POST size than the 2M limit. What is the downside of setting this to large value or -1 (unlimited) to
max-post-sizeandmax-save-post-sizein EAP 6?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 4.x
- 5.x
- 6.x
- 7.x
- JBossWeb
- Tomcat
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
