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

Automatic HEAD requests breaks subsequent request(s) on resteasy-netty4 and resteasy-vertx

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.0.22.Final, 3.1.2.Final
    • 3.1.1.Final
    • None
    • None

    Description

      When using resteasy-netty4, it seems that automatic HEAD handling as specified by JAXRS is faulty.

      We use a GET /healthcheck endpoint to monitor our services. When our monitoring tool (monit) switched to using HEAD by default when sending requests, we started to notice strange behavior from our APIs. Random errors and what seemed to be corrupted responses.

      When we looked into it, we found out that the response body of the /healthcheck was prepended to the response of faulty responses. So we thought it might have been related to resteasy somehow.

      It seems that when issue 1365 was fixed, it introduced this behavior. I think, but Im not sure at all, that it may be the NettyResponse buffer that is not properly cleaned and may leak into a subsequent response.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. 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.
          • Closed
          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

              rhn-support-asoldano Alessio Soldano
              rsertelon Romain Sertelon (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: