[jboss-jira] [JBoss JIRA] (WFLY-6437) Undertow listener max-post-size attribute default value discrepancy

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas moved JBEAP-3986 to WFLY-6437:
---------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-6437  (was: JBEAP-3986)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Web (Undertow)
                           (was: Web (Undertow))
       Target Release:   (was: 7.0.0.GA)
    Affects Version/s: 10.0.0.Final
                           (was: 7.0.0.ER7)


> Undertow listener max-post-size attribute default value discrepancy
> -------------------------------------------------------------------
>
>                 Key: WFLY-6437
>                 URL: https://issues.jboss.org/browse/WFLY-6437
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 10.0.0.Final
>            Reporter: Stuart Douglas
>            Assignee: Stuart Douglas
>
> There is a discrepancy in undertow schema definition of listener attribute 'max-post-size' [default value here|https://github.com/jbossas/jboss-eap7/blob/EAP_7.0.0.ER7-dev/undertow/src/main/resources/schema/wildfly-undertow_3_1.xsd#L91] and [ListenerResourceDefinition here|https://github.com/jbossas/jboss-eap7/blob/EAP_7.0.0.ER7-dev/undertow/src/main/java/org/wildfly/extension/undertow/ListenerResourceDefinition.java#L141].
> These two default values should be unified so they match.
> NOTE: I set GA as a target release as this is probably trivial change in Undertow schema definition which is better to do before GA as after that any change into schema is difficult.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)