So, two questions: 1) my Z2.log is growing continuously, and that would not be strictly a problem; but now it's 1.3Gb.. and i can expect him to grow more and more... My ambition is not to full entire disk space for the logs, but as i know, i can't avoid to keep them! The content of Z2.log is plain text, and i can suppose that using some sort of compression method probably might lead to an high rate compression of Z2.log. It would be great if Medusa could handle compressed Z2.log. Is there a way to accomplish this? 2) In Zope v. >= 2.6.0 has been implemented this nice feature: "Gzip content compression when serving pages" (http://www.zope.org/Products/Zope/2.6.0/announce) It's supposed that gzip feature is enabled by default; well, how to obtain statistic about compression?(i.e. size of html page after compression, maybe the ratio and so on...) With mod_gzip for Apache there was the possibility to specify something like: LogFormat "%h %l %u %t \"%r\" %>s %b mod_gzip: %{mod_gzip_result}n In:%{mod_gzip_input_size}n Out:%{mod_gzip_output_size}n:%{mod_gzip_compression_ratio}npct." common_with_mod_gzip_info2 and CustomLog /usr/local/apache/logs/access.log common_with_mod_gzip_info2 Does Medusa allow something similar? Thanks all, Paolo Dina