Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10026

(7.0.z) Upgrade undertow from 1.3.28.Final to 1.3.29.Final

    XMLWordPrintable

Details

    • Component Upgrade
    • Resolution: Done
    • Major
    • 7.0.8.CR1, 7.0.8.GA
    • None
    • Build System
    • None
    • EAP 7.0.8

    Attachments

      Issue Links

        clones

        Component Upgrade - A task tracking an update to a bundled component JBEAP-10014 (7.0.z) Upgrade undertow from 1.3.28.Final-redhat-1 to 1.3.28.Final-redhat-4

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Verified
        incorporates

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-9709 (7.0.z) UNDERTOW-1011 - Undertow doesn't process HTTPS request sometimes

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Verified

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-9874 [GSS](7.0.z) UNDERTOW-884 FormAuthenticationMechanism.sendRedirect computes wrong location header value

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Verified

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-10143 (7.0.z) UNDERTOW-1040 Request scheme attribute is not writable

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Verified

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-10150 [GSS] (7.0.z) UNDERTOW-1021 - AJP listener should log at DEBUG level when handling 400 Bad Request like wrong magic number and invalid Content-Length

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Verified

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-10173 [GSS](7.0.z) UNDERTOW-898 Failover targets should be chosen deterministically (Undertow)

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Verified

        Bug - A problem which impairs or prevents the functions of the product. JBEAP-11830 (7.0.z) UNDERTOW-1020 AjpRequestParser does not output any log message when exceeding max-parameters/max-headers

        • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
        • Verified
        is related to

        Component Upgrade - A task tracking an update to a bundled component JBEAP-11773 [GSS](7.0.z) Upgrade undertow from 1.3.29.Final to 1.3.31.Final

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Verified

        Activity

          People

            vdosoudi@redhat.com Vladimir Dosoudil
            spyrkob Bartosz Spyrko-Smietanko
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: