Bug 844858
| Summary: | tar.gz is turned off by default for JBoss | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Steven Citron-Pousty <spousty> |
| Component: | Image | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.x | CC: | bmeng, bparees, dmcphers, jhou |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-24 03:33:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I've updated the JBoss config Tested on devenv_2484
Steps:
1. Ssh into instance, check jboss config has been updated according to fix.
Also check /etc/httpd/conf.d/jboss_compression.conf has enabled apache compression.
2. Create jboss applications
3. Access app's webset, check http headers, verify they are using gzip encoding:
<------------Request Headers------------>
Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Charset:UTF-8,*;q=0.5
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:max-age=0
Host:jbosseap1-2484t.dev.rhcloud.com
If-Modified-Since:Fri, 16 Nov 2012 02:14:49 GMT
Proxy-Connection:keep-alive
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4
<------------Response Headers------------>
Response Headersview source
Connection:keep-alive
Date:Fri, 16 Nov 2012 02:28:17 GMT
ETag:W/"6759-1353032089000"
Server:Apache-Coyote/1.1
Vary:Accept-Encoding,User-Agent
Via:1.0 file.rdu.redhat.com (squid/3.1.10)
X-Cache:HIT from file.rdu.redhat.com
X-Cache-Lookup:HIT from file.rdu.redhat.com:8080
I didn't find it using gzip encoding.
So I have added following in .openshift/config/standalone.xml and git push
</extensions>
<system-properties>
<property name="org.apache.coyote.http11.Http11Protocol.COMPRESSION" value="on"/>
</system-properties>
<management>
This time, the response headers tells me my application is using gzip encoding.
<----------Response Headers----------->
Accept-Ranges:bytes
Age:562
Connection:keep-alive
Content-Encoding:gzip
.......
According to comment 1, it's not turned on by default, have to turn it on by configuring standalone.xml manually, and there is also no fix for jbossews
So, assign this bug back, thanks!
Updated standalone.xml Tested on devevn-stage_257 standalone.xml got updated for jbossas and jbosseap. But I found this issue: After a jbossas/jbosseap application is firstly created, accessing app's website, open development tool of chrome, refresh, the Response Headers does not indicate that it is using gzip encoding. Like this: <----------Response Headers-----------> Connection:Keep-Alive Date:Tue, 20 Nov 2012 02:12:44 GMT ETag:W/"6759-1353377475000" Keep-Alive:timeout=15, max=98 Server:Apache-Coyote/1.1 Vary:Accept-Encoding,User-Agent After git pushing this app, then access app's website again, the Response Headers shows that is is using gzip encoding. Like this: <----------Response Headers-----------> Connection:Keep-Alive Content-Encoding:gzip Content-Length:20 Date:Tue, 20 Nov 2012 02:05:40 GMT Keep-Alive:timeout=15, max=100 ProxyTime:D=376174 Server:Apache-Coyote/1.1 Strict-Transport-Security:max-age=15768000, includeSubDomains Vary:Accept-Encoding,User-Agent Actual result now is: gzip encoding for jbossas/jbosseap is enabled after first git push, so assign it back to see if we need further fix, thanks! I ran this test using jbossap-7 and it seems to be working: 1) rhc app create jbossapp jbossas-7 2) curl -v -H "Accept-Encoding:gzip,deflate,sdch" http://jbossapp-test.dev.rhcloud.com >& out 3) view "out" file: Header is sent: * About to connect() to jbossapp-test.dev.rhcloud.com port 80 (#0) * Trying 54.204.80.236... * Connected to jbossapp-test.dev.rhcloud.com (54.204.80.236) port 80 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.29.0 > Host: jbossapp-test.dev.rhcloud.com > Accept: */* > Accept-Encoding:gzip,deflate,sdch Response is compressed: < HTTP/1.1 200 OK < Date: Wed, 27 Nov 2013 18:11:21 GMT < Server: Apache-Coyote/1.1 < Accept-Ranges: bytes < ETag: W/"41833-1385575868000" < Last-Modified: Wed, 27 Nov 2013 18:11:08 GMT < Content-Type: text/html; charset=UTF-8 < Content-Encoding: gzip < Vary: Accept-Encoding,User-Agent < ProxyTime: D=305089 < Transfer-Encoding: chunked Can you confirm this is still not working? I think we can close this. Tested on devenv_4080, Both jbossas and jbosseap can response with gzip encoding by default when request contains gzip encoding. # curl -H "Accept-Encoding:gzip,deflate,sdch" -vI http://jbas1-bmengdev.dev.rhcloud.com > Accept-Encoding:gzip,deflate,sdch < HTTP/1.1 200 OK < Content-Type: text/html; charset=UTF-8 < Content-Encoding: gzip # curl -H "Accept-Encoding:gzip,deflate,sdch" -vI http://jbeap1-bmengdev.dev.rhcloud.com > Accept-Encoding:gzip,deflate,sdch < HTTP/1.1 200 OK < Content-Type: text/html; charset=UTF-8 < Content-Encoding: gzip |
Description of problem: gzipping of content is one of the most recommended ways to improve web site performance. It also lowers the size of the network traffic from the server. There is a filter for JBoss that automatically compresses output if the browser says it can accept gzipped content. Can we please turn it on by default. The JBoss team confirmed that there is no performance problems from this. From the email thread: On 07/16/2012 06:44 PM, Steven Citron-Pousty wrote: Greetings Jean-Frederic: Currently on OpenShift output is not being gzipped even when the browser tells the server it supports it. So there are two questions: 1) Developers want to turn this on for their jboss instance. What does that look like in the config file? In the standalone.xml set the system property org.apache.coyote.http11.Http11Protocol.COMPRESSION to on like below: +++ </extensions> <system-properties> <property name="org.apache.coyote.http11.Http11Protocol.COMPRESSION" value="on"/> </system-properties> <management> +++ 2) Shouldn't we have this turned on by default for JBOSS since it is recommended best practice for web sites. If not, then why not? It is not on by default in Apache httpd so we do the same. To get it in the Apache httpd you need to add something like AddOutputFilterByType DEFLATE text/html or <files *.html> SetOutputFilter DEFLATE </files> Cheers Jean-Frederic Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: