10 a.m.
rupesh kumar [https://community.jboss.org/people/er_rupeshmca] created the discussion
"Re: Regarding Https Compression (on Chrome Browser)"
To view the discussion, visit: https://community.jboss.org/message/750498#750498
--------------------------------------------------------------
Yes now I have applied compression=force and also Mimetypes, But Still now it is showing
the same message on chrome as previously..
<Server>
<!-- Optional listener which ensures correct init and shutdown of APR,
and provides information if it is not installed -->
<Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
<!--Initialize Jasper prior to webapps are loaded. Documentation at
/docs/jasper-howto.html -->
<Listener className="org.apache.catalina.core.JasperListener" />
<Service name="jboss.web">
<!-- A HTTP/1.1 Connector on port 8080
<Connector protocol="HTTP/1.1" port="8080"
address="${jboss.bind.address}"
connectionTimeout="20000" redirectPort="8443" />
-->
<Connector port="8080" address="${jboss.bind.address}"
maxThreads="250"
maxHttpHeaderSize="8192" emptySessionPath="true"
protocol="HTTP/1.1"
enableLookups="false" redirectPort="8443"
acceptCount="100" connectionTimeout="20000"
*compressableMimeType="text/html,text/xml,text/css,text/javascript,
application/x-javascript,application/javascript"*
disableUploadTimeout="true"
*compression="force"*></Connector>
<!-- Add this option to the connector to avoid problems with
.NET clients that don't implement HTTP/1.1 correctly
restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$"
-->
<!-- A AJP 1.3 Connector on port 8009 -->
<Connector protocol="AJP/1.3" port="8009"
address="${jboss.bind.address}"
redirectPort="8443" />
<!-- SSL/TLS Connector configuration using the admin devl guide keystore -->
<Connector protocol="HTTP/1.1" SSLEnabled="true"
port="8443" address="${jboss.bind.address}"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"
keystorePass="rmi+ssl" sslProtocol = "TLS" />
Can you Suggest on this?
Should i have to add compression parameter in SSL/TLS Connection Configuration and AJP
Connector Also ?
Regards
Rupesh
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/750498#750498]
Start a new discussion in Performance Tuning at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:37 a.m.
Radoslav Husar [https://community.jboss.org/people/rhusar] created the discussion
"Re: Regarding Https Compression (on Chrome Browser)"
To view the discussion, visit: https://community.jboss.org/message/750515#750515
--------------------------------------------------------------
Should i have to add compression parameter in SSL/TLS Connection
Configuration and AJP Connector Also ?
Yes! That seems to be the glitch. You have
enabled compression on the "wrong" connector. Direct your browser to
localhost:8080 to test if you enabled successfully but you probably want to configure the
same items on the HTTPS connector (running on port 8443).
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/750515#750515]
Start a new discussion in Performance Tuning at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:09 a.m.
rupesh kumar [https://community.jboss.org/people/er_rupeshmca] created the discussion
"Re: Regarding Https Compression (on Chrome Browser)"
To view the discussion, visit: https://community.jboss.org/message/750709#750709
--------------------------------------------------------------
I have changed http port 8080 to port 80 and SSL port from 8443 to 443
i have also configure Https port and add compression , please find below configured
file..
Server>
<!-- Optional listener which ensures correct init and shutdown of APR,
and provides information if it is not installed -->
<Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
<!--Initialize Jasper prior to webapps are loaded. Documentation at
/docs/jasper-howto.html -->
<Listener className="org.apache.catalina.core.JasperListener" />
<Service name="jboss.web">
<!-- A HTTP/1.1 Connector on port 8080 -->
<Connector protocol="HTTP/1.1" port="80"
address="${jboss.bind.address}" *compression="force"*
noCompressionUserAgents="gozilla, traviata"
*
compressableMimeType="text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript,image/svg+xml,text/json,gzip"*
* connectionTimeout="20000" redirectPort="443" />*
<!-- Add this option to the connector to avoid problems with
.NET clients that don't implement HTTP/1.1 correctly
restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$"
-->
<!-- A AJP 1.3 Connector on port 8009 -->
<Connector protocol="AJP/1.3" port="8009"
address="${jboss.bind.address}"
redirectPort="443" />
<!-- SSL/TLS Connector configuration using the admin devl guide keystore -->
<Connector protocol="HTTP/1.1" SSLEnabled="true"
port="443" address="${jboss.bind.address}"
maxThreads="20" strategy="ms"
maxHttpHeaderSize="8192"
emptySessionPath="true"
*
compressableMimeType="text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript,image/svg+xml,text/json,gzip"*
* compression="force"*
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"
keystorePass="rmi+ssl" sslProtocol = "TLS" />
<Engine name="jboss.web" defaultHost="localhost">
But still issue not resolved on https but in http the content is showing compressed with
wbox command
i check the compressed content with wbox command utility
[monitor@app classes]$ wbox http://192.168.149.24:80/cdotmain/
http://192.168.149.24:80/cdotmain/ compr
WBOX 192.168.149.24 (192.168.149.24) port 80 [compr]
0. 200 OK 781 bytes 1 ms compr
1. 200 OK 781 bytes 1 ms compr
2. 200 OK 781 bytes 1 ms compr
3. 200 OK 781 bytes 1 ms compr
And then check on on Https when application redirect from port 80 to 443.
[monitor@app classes]$ wbox https://192.168.149.24:443/TMRS/
https://192.168.149.24:443/TMRS/ compr
WBOX 192.168.149.24 (192.168.149.24) port 443 [compr]
0. 0 () 7 bytes 1 ms
1. 0 () 7 bytes 0 ms
2. 0 () 7 bytes 0 ms
3. 0 () 7 bytes 0 ms
4. 0 () 7 bytes 0 ms
5. 0 () 7 bytes 0 ms
Please suggest
thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/750709#750709]
Start a new discussion in Performance Tuning at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:14 a.m.
rupesh kumar [https://community.jboss.org/people/er_rupeshmca] created the discussion
"Re: Regarding Https Compression (on Chrome Browser)"
To view the discussion, visit: https://community.jboss.org/message/751148#751148
--------------------------------------------------------------
I have changed http port 8080 to port 80 and SSL port from 8443 to 443
i have also configure Https port and add compression , please find below configured
file..
Server>
<!-- Optional listener which ensures correct init and shutdown of APR,
and provides information if it is not installed -->
<Listener className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
<!--Initialize Jasper prior to webapps are loaded. Documentation at
/docs/jasper-howto.html -->
<Listener className="org.apache.catalina.core.JasperListener" />
<Service name="jboss.web">
<!-- A HTTP/1.1 Connector on port 8080 -->
<Connector protocol="HTTP/1.1" port="80"
address="${jboss.bind.address}" *compression="force"*
noCompressionUserAgents="gozilla, traviata"
*
compressableMimeType="text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript,image/svg+xml,text/json,gzip"*
* connectionTimeout="20000" redirectPort="443" />*
<!-- Add this option to the connector to avoid problems with
.NET clients that don't implement HTTP/1.1 correctly
restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$"
-->
<!-- A AJP 1.3 Connector on port 8009 -->
<Connector protocol="AJP/1.3" port="8009"
address="${jboss.bind.address}"
redirectPort="443" />
<!-- SSL/TLS Connector configuration using the admin devl guide keystore -->
<Connector protocol="HTTP/1.1" SSLEnabled="true"
port="443" address="${jboss.bind.address}"
maxThreads="20" strategy="ms"
maxHttpHeaderSize="8192"
emptySessionPath="true"
*
compressableMimeType="text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript,image/svg+xml,text/json,gzip"*
* compression="force"*
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"
keystorePass="rmi+ssl" sslProtocol = "TLS" />
<Engine name="jboss.web" defaultHost="localhost">
But still issue not resolved on https but in http the content is showing compressed with
wbox command
i check the compressed content with wbox command utility
[monitor@app classes]$ wbox http://192.168.149.24/cdotmain/
http://192.168.149.24:80/cdotmain/ compr
WBOX 192.168.149.24 (192.168.149.24) port 80 [compr]
0. 200 OK 781 bytes 1 ms compr
1. 200 OK 781 bytes 1 ms compr
2. 200 OK 781 bytes 1 ms compr
3. 200 OK 781 bytes 1 ms compr
And then check on on Https when application redirect from port 80 to 443.
[monitor@app classes]$ wbox https://192.168.149.24/TMRS/ https://192.168.149.24:443/TMRS/
compr
WBOX 192.168.149.24 (192.168.149.24) port 443 [compr]
0. 0 () 7 bytes 1 ms
1. 0 () 7 bytes 0 ms
2. 0 () 7 bytes 0 ms
3. 0 () 7 bytes 0 ms
4. 0 () 7 bytes 0 ms
5. 0 () 7 bytes 0 ms
Please suggest
thanks.
Please help.........
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/751148#751148]
Start a new discussion in Performance Tuning at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:44 a.m.
Radoslav Husar [https://community.jboss.org/people/rhusar] created the discussion
"Re: Regarding Https Compression (on Chrome Browser)"
To view the discussion, visit: https://community.jboss.org/message/751614#751614
--------------------------------------------------------------
It looks as though there is a problem with understanding of what chrome is saying. If you
do the steps that you did, just look at the response headers:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
Accept-Ranges: bytes
ETag: W/"1406-1328876700000"
Last-Modified: Fri, 10 Feb 2012 12:25:00 GMT
Content-Type: text/html
Transfer-Encoding: chunked
*Content-Encoding: gzip*
Vary: Accept-Encoding
Date: Thu, 02 Aug 2012 08:18:12 GMT
You see that the content is compressed with
gzip.
However, in chrome you will still see:
Your connection to localhost is encrypted with 128-bit encryption.
The connection uses TLS 1.0.
The connection is encrypted using AES_128_CBC, with SHA1 for message authentication and
DHE_RSA as the key exchange mechanism.
The connection is not compressed.
This is because chrome is talking about SSL
stream-level compression. You can read some here
http://www.belshe.com/2010/11/18/ssl-compression-and-you/
http://www.belshe.com/2010/11/18/ssl-compression-and-you/
Here is a small excerpt:
One aspect of http://en.wikipedia.org/wiki/Secure_Sockets_Layer SSL
which many people are not aware of is that SSL is capable of compressing the entire SSL
stream. The authors of SSL knew that if you’re going to encrypt data, you need to
compress it before you encrypt it, since well-encrypted data tends to look pretty random
and non-compressible. But even though SSL supports compression, no browsers support it.
Except Chrome 6 & later.
Generally, stream-level compression at the SSL layer is not ideal. Since SSL doesn’t
know what data it is transporting, and it could be transporting data which is already
compressed, such as a JPG file, or GZIP content from your web site. And
double-compression is a waste of time. Because of this, historically, no browsers
compressed at the SSL layer – we all felt certain that our good brothers on the server
side would solve this problem better, with more optimal compression.
To enable this
in JBoss/Tomcat you need to use jboss/tomcat natives (openssl).
Rado
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/751614#751614]
Start a new discussion in Performance Tuning at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4549
days inactive
4556
days old
4 comments
2 participants
participants (2)
-
Radoslav Husar -
rupesh kumar