Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-2116

ServletOutputStreamImpl incorrectly sets Content-Length to 0

    XMLWordPrintable

Details

    Description

      When using an asynchronous WriteListener, the ServletOutputStreamImpl assumes that if not content has been written, the Content-Length header should be set to 0. See https://github.com/undertow-io/undertow/blob/20d777c181264f749a39fca7003dc9441687faa9/servlet/src/main/java/io/undertow/servlet/spec/ServletOutputStreamImpl.java#L680

      Unfortunately, this has the side effect that HEAD requests, for which no response body should be written, always end up with Content-Length 0. Even when the servlet sets the Content-Length header correctly, to whatever value you would have for a GET request.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-23796 [QA](7.4.z) UNDERTOW-2116 - java.lang.AssertionError: Content-Encoding header should be defined

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is caused by

          Bug - A problem which impairs or prevents the functions of the product. UNDERTOW-2070 Empty reply from Undertow if sendRedirect is called after setting 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.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component WFCORE-6057 Upgrade Undertow to 2.3.0.Final (CVE-2022-2764)

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: UNDERTOW

              People

                rhn-support-rmartinc Ricardo Martin Camarero
                apoutsma Arjen Poutsma (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: