Bug 1455619 - [GSS] (6.4.z) Cannot set max-save-post-size to -1
Summary: [GSS] (6.4.z) Cannot set max-save-post-size to -1
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.4.15
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Radim Hatlapatka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-25 15:43 UTC by Robert Bost
Modified: 2021-08-30 12:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-01 01:47:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3103221 0 None None None 2017-07-03 18:37:39 UTC

Description Robert Bost 2017-05-25 15:43:21 UTC 
Description of problem: JBossWeb allows for the max save post size to be -1 but the web subsystem connector config validator blocks negative values.



Version-Release number of selected component (if applicable): reproduced in jboss-eap 6.x branch.


How reproducible: Always.


Steps to Reproduce:
1. Configure http connector like: <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" max-save-post-size="-1"/>
2. Start JBoss 
3. Failure to start due to ParseError

Actual results: ParseError and JBoss EAP fails to start.


Expected results: JBoss EAP should accept the -1 value.


Additional info:
Comment 1 Robert Bost 2017-05-25 16:24:12 UTC 
Pull request https://github.com/jbossas/jboss-eap/pull/2998
Note You need to log in before you can comment on or make changes to this bug.