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

ETag not quoted in ResponseBuilder.tag(String tag)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 3.0.19.Final
    • 2.3.5.Final, 3.0.18.Final
    • jaxrs

    Description

      Response.status(412).entity(message).tag("123").build() should generate ETag: "123" but instead does not quote the tag ETag: 123.

      The JAX-RS spec says that the ETag should be quoted by the runtime. Jersey adheres to the spec here, RESTEasy doesn't.

      ResponseBuilder.tag(EntityTag tag) method works corrrectly but ResponseBuilder.tag(String tag) has this bug

      Attachments

        Issue Links

          clones

          Bug - A problem which impairs or prevents the functions of the product. RESTEASY-803 ETag not quoted in Response

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

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-5211 (7.1.0) ETag not quoted in ResponseBuilder.tag(String tag)

          • 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

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-5446 (7.0.z) RESTEASY-1439 - ETag not quoted in ResponseBuilder.tag(String tag)

          • 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

          Activity

            People

              rhn-support-asoldano Alessio Soldano
              bedrin_jira Dmitry Bedrin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 hours
                  4h
                  Remaining:
                  Time Spent - 2 hours Remaining Estimate - 1 hour
                  1h
                  Logged:
                  Time Spent - 2 hours Remaining Estimate - 1 hour Time Not Required
                  2h