Hi Kevin/Ralf/etc., Until recently, it was impossible to manipulate Apache responses (other than static content which a module can be written to serve) without patching the core Apache. Apache 2.0 tries to overcome this problem, but modules like mod_ssl had to insert many patches into the core source, a painful requirement, and also a dependency on any version of Apache, and need to update mod_ssl for any new version of Apache. mod_gzip pretends to solve this problem. According to its documentation, it manipulates not only statis files, but also the output of other modules. It comes as one C file (Apache module), without patching anything else. I'd appreciate if there are answers for my humble questions: 1. Am I wrong? Or the "trick" was finally found? 2. Can this trick be used for other purposes? (such as SSL; Such a trick may be used to avoid the EAPI patches which are inserted into the core source of Apache) 3. Does mod_gzip and mod_ssl (the current) run together? Or is there any conflict? 4. Is there any cost for this trick? (i.e. is EAPI/etc. more efficient?) 5. Can your trick be used to manipulate the input (a.k.a. HTTP requests) and headers too? 6. Is there any conflict with mod_proxy? Can mod_gzip run together with mod_proxy? Does it gzip its output too? (so you may add a reverse proxy to an existing web server, without touching it, but only speeding the output by compressing it externally) BTW: mod_proxy has been always HTTP/1.0 which is not supported by gzip, but recently ported to support 1.1 as well. Thanks in advance, -- Eli Marmor [EMAIL PROTECTED] CTO, Founder Netmask (El-Mar) Internet Technologies Ltd. __________________________________________________________ Tel.: +972-9-766-1020 8 Yad-Harutzim St. Fax.: +972-9-766-1314 P.O.B. 7004 Mobile: +972-50-23-7338 Kfar-Saba 44641, Israel ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
