Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-1365

HEAD requests always return Content-Length: 0

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.0.19.Final
    • 3.0.16.Final
    • jaxrs
    • None

    Description

      Per HTTP spec, responses to HEAD requests should include Content-Length header indicating the entity size even though the entity itself is not included in response. Generic javax.servlet.http.HttpServlet.doHead() supports this as well.

      However, RESTEasy skips the entity serialization for HEAD requests and thus returns the wrong Content-Length: 0. In org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse():

            if (jaxrsResponse.getEntity() == null || request.getHttpMethod().equalsIgnoreCase("HEAD"))
      {
         response.setStatus(jaxrsResponse.getStatus());
         commitHeaders(jaxrsResponse, response);
         return;
      }

      Note this happens after the resource method already built the response, so all we're saving here is serialization – the heavy lifting of building the response already occurred.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1627 Automatic HEAD requests breaks subsequent request(s) on resteasy-netty4 and resteasy-vertx

          • 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.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4671 (7.1.0) HEAD requests always return Content-Length: 0

          • 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
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5447 (7.0.z) RESTEASY-1365 - HEAD requests always return Content-Length: 0

          • 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
          relates to

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-1632 Improve header processing in response to HEAD requests

          • 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.
          • Open

          Activity

            People

              istudens@redhat.com Ivo Studensky
              pnehrer_jira Peter Nehrer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: