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

@GZIP annotation on client proxy doesn't set content-type gzip to the request header

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR13
    • 7.1.0.DR4
    • REST
    • Hide

      git clone git@github.com:kanovotn/Resteasy.git
      git checkout "testsuite/GzipPost"
      cd testsuite
      mvn clean verify -Djboss.home=PATH_TO_EAP -Dtest=GzipTest -fn -Dmaven.test.redirectTestOutputToFile=false -Dversion.resteasy.testsuite=3.0.19.Final-redhat-1

      Show
      git clone git@github.com:kanovotn/Resteasy.git git checkout "testsuite/GzipPost" cd testsuite mvn clean verify -Djboss.home=PATH_TO_EAP -Dtest=GzipTest -fn -Dmaven.test.redirectTestOutputToFile=false -Dversion.resteasy.testsuite=3.0.19.Final-redhat-1

    Description

      I have a client proxy interface which has @GZIP annotation to send a request with gzip compression. See steps to reproduce and this [1] test.

      @Path("/gzippost")
          public interface GzipProxy {
              @Consumes("application/json")
              @POST
              public Response post(@GZIP Pair pair);
          }
      

      Using resteasy client 3.0.19.Final-redhat-1 client, there is no Content-Encoding header in the request.
      Using latest resteasy client from upstream the requests contains header "Content-Encoding: gzip".

      [1] https://github.com/kanovotn/Resteasy/blob/master/testsuite/integration-tests/src/test/java/org/jboss/resteasy/test/core/interceptors/GzipTest.java

      Attachments

        Issue Links

          Activity

            People

              rhn-support-iweiss Ingo Weiss
              kanovotn Katerina Odabasi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 3 days
                  3d
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 days
                  3d