Thank you.
Sorry for long delay after your responses.
Simply setting SetOutputFilter DEFLATE also did work for me.
previously I tried
AddOutputFilterByType DEFLATE text/html ...etc...
Though it worked for static resources it failed to deflate dynamic
ones. Maybe that is because apache doesn't
On 14 Feb 2011, at 18:27, Gennady Kushnir wrote:
It is not Wonder app.
Why make such tricks whereas Apache should do that already?
Because you might be using WebObjects without Apache.
Is this a module load order problem? Which version of Apache have
you got? Is mod_deflate.so loaded
Hi Gennady;
Why make such tricks whereas Apache should do that already?
Because you might be using WebObjects without Apache.
Another reason (depending on your deployment) is that you may have a
number of application servers with ample CPU resource, but one
web-server/load-balancer with
On 15 Feb 2011, at 09:54, Patrick Middleton wrote:
On 14 Feb 2011, at 18:27, Gennady Kushnir wrote:
...
Is this a module load order problem? Which version of Apache have
you got? Is mod_deflate.so loaded before mod_WebObjects.so, or after?
Further research reveals that while module
Hello list!
I've just tried to compress traffic produced by my WOApp but I only
succeeded in compressing static resources (css and js).
Here is my configuration fragment.
IfModule mod_deflate.c
AddOutputFilterByType DEFLATE text/html application/xhtml+xml
text/plain text/xml \
If it's a Wonder app, add this to you Properties and you're done:
er.extensions.ERXApplication.responseCompressionEnabled=true
Timo
Am 14.02.2011 um 09:59 schrieb Gennady Kushnir:
Hello list!
I've just tried to compress traffic produced by my WOApp but I only
succeeded in compressing static
It is not Wonder app.
Why make such tricks whereas Apache should do that already?
2011/2/14 Timo Hoepfner th-...@onlinehome.de:
If it's a Wonder app, add this to you Properties and you're done:
er.extensions.ERXApplication.responseCompressionEnabled=true
Timo
Am 14.02.2011 um 09:59 schrieb
