Antwort: [Mod_gzip] mod_gzip excluding port 443

[Douglas Kirkland]

On Wednesday 16 October 2002 10:50 am, Michael.Schroepl@telekurs.de wrote:
> Hi Douglas,
>
> > Each virtual host can be accessed through ssl and without ssl.
>
> How is this working?
> Could you give us a configuration example for one virtual host?

<VirtualHost *:80 *:443>
  ServerName www.dev4.dnsrx.net
  ServerAlias dev4.dnsrx.net
  ServerAdmin webmaster@dev4.dnsrx.net
  TransferLog /usr/local/apache/vhosts/dev4.dnsrx.net/logs/access_log
  ErrorLog /usr/local/apache/vhosts/dev4.dnsrx.net/logs/error_log
  LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""
  DocumentRoot /usr/local/apache/vhosts/dev4.dnsrx.net/htdocs
  ScriptAlias /cgi-bin/ /usr/local/apache/vhosts/dev4.dnsrx.net/cgi-bin/
 **snip**
</VirtualHost>


>
> > I am wondering on the next upgrade of mod_gzip if a port exclude can
> > be added as an option.
> > For example a line in the config for mod-gzip can look like this:
> > mod_gzip_item_exclude port 443
>
> If Apache can tell apart the port relevant sections within a
> virtual host, you can just enable mod_gzip in one section and
> disable it in another section - so there is no need for another
> configuration directive.
> And if Apache cannot tell these calls from each other, how
> should mod_gzip?

Yes apache can tell them apart.  My question is why do we need uri, mines, 
and files options for excluding.  They all can be configured with different 
server domain blocks.  They are all there to make our life easer.  I have a 
global configuration for mod_gzip that works on each virtual domain server 
block.  This way I do not have to edit each server domain block on each 
server.

Thanks,

-- 
Douglas Kirkland,  Systems Administrator
Technical Support Department
Rhyton Corporation
tech@rhyton.com
http://www.rhyton.com