Hi
We're serving commonly used js libs under http://toolserver.org/~osm/libs/
but the toolserver is serving out the js files uncompressed [1]. GZ Compression reduces the size of openlayers from 923.66 KB to 207.08 KB (77.58%) so it is really necessary to enable this.
How can we achieve this?
Peter
Peter Körner wrote:
Hi
We're serving commonly used js libs under http://toolserver.org/~osm/libs/
but the toolserver is serving out the js files uncompressed [1]. GZ Compression reduces the size of openlayers from 923.66 KB to 207.08 KB (77.58%) so it is really necessary to enable this.
How can we achieve this?
Peter
According to [1] you would add the directive ContentCompressionEnabled application/x-javascript
1- http://support.zeus.com/zws/media/docs/4.2/ZWSUserGuide.pdf
Am 03.11.2010 21:52, schrieb Platonides:
According to [1] you would add the directive ContentCompressionEnabled application/x-javascript
There are known bugs with some versions of IE and compressed JS so they need to be excluded somehow, see http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
Peter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Körner:
There are known bugs with some versions of IE and compressed JS so they need to be excluded somehow, see http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
According to that page, MSIE has no problems with compressed content, but Netscape 4.x won't handle it. I am fairly certain that NS4 won't work very well with OpenLayers anyway.
- river.
Am 04.11.2010 09:43, schrieb River Tarnell:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Körner:
There are known bugs with some versions of IE and compressed JS so they need to be excluded somehow, see http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
According to that page, MSIE has no problems with compressed content, but Netscape 4.x won't handle it. I am fairly certain that NS4 won't work very well with OpenLayers anyway.
You're right, I'm sorry. Is there a way to enable js compression? Should I open a jira ticket?
My experience with jira tickets is that they often are ignored / not completed, so I asked here.
Peter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Körner:
You're right, I'm sorry. Is there a way to enable js compression?
Did the solution Platonides suggested not work?
- river.
Am 04.11.2010 10:53, schrieb River Tarnell:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Körner:
You're right, I'm sorry. Is there a way to enable js compression?
Did the solution Platonides suggested not work?
Where am I supposed to put the line? I created a .htacces in the libs folder (this would be the way do to it with apache) but it does not have an effect. I'm not familar with Zeus configuration.
Peter
Am 03.11.2010 21:52, schrieb Platonides:
According to [1] you would add the directive ContentCompressionEnabled application/x-javascript
1- http://support.zeus.com/zws/media/docs/4.2/ZWSUserGuide.pdf
I tried to use this directive in various ways in .htaccess files in various places but it did not seem to have any impact. Any ideeas?
Peter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Körner:
I tried to use this directive in various ways in .htaccess files in various places but it did not seem to have any impact. Any ideeas?
I have enable compression globally for:
text/plain text/html application/x-javascript
It might be that since compression wasn't enable at all, the .htaccess directive was ignored.
- river.
Am 08.11.2010 13:04, schrieb River Tarnell:
It might be that since compression wasn't enable at all, the .htaccess directive was ignored.
It seems so, because now I can toggle compression for css on and off by setting ContentCompressionEnabled text/css in the htaccess file.
Thank you for fixing this.
Peter
toolserver-l@lists.wikimedia.org