Bug 1455619

Summary:	[GSS] (6.4.z) Cannot set max-save-post-size to -1
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Robert Bost <rbost>
Component:	Web	Assignee:	jboss-set
Status:	CLOSED WONTFIX	QA Contact:	Radim Hatlapatka <rhatlapa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.4.15	CC:	aogburn, bmaxwell, brian.stansberry, rmaucher
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-01 01:47:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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