1 Reply Latest reply on Jun 30, 2011 11:02 PM by hotribao

    seam-remoting response not compressed

    hotribao
      I am using seam-remoting to make ajax calls. I enabled gzip compression on tomcat server by setting compression="on" on the "Connector" tag (in server.xml) as following:

          <Connector compression="on" connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443"/>

      However, when I view the response header using FireBug, the response seem not to be compressed. Below is what I see with Firebug:

      Server     Apache-Coyote/1.1
      Content-Type     text/xml
      Content-Length     1589
      Date     Thu, 30 Jun 2011 10:26:13 GMT

      In other "traditional" seam ajax response (not seam-remoting), the responses are compressed. Bellow is what I see with Firebug for those reponses:

      Server     Apache-Coyote/1.1
      X-Powered-By     JSF/1.2
      Ajax-Response     true
      Cache-Control     no-cache, must-revalidate, max_age=0, no-store
      Expires     0
      Pragma     no-cache
      Content-Type     text/xml;charset=UTF-8
      Transfer-Encoding     chunked
      Content-Encoding     gzip
      Vary     Accept-Encoding
      Date     Thu, 30 Jun 2011 10:42:52 GMT

      Did I miss something in the configurations?

      --------------
      seam version 2.2.1.CR1
      tomcat 6
        • 1. Re: seam-remoting response not compressed
          hotribao

          I found myself the answer for my question. It turns out that there is a mininum size (which I don't know how many) which trigger the compression on tomcat. Below that size, the response is not compressed. I try to make my seam-remoting response bigger, then I can see it gziped