[Mod_gzip] mod_gzip excluding port 443

[Glenn]

<rant>
Argh.  I dislike duplicated Re:'s and Antw:'s
</rant>


Douglas, how about some simplicity using web server proxies:


                 /--- httpd (443) ---\
                /       proxy         \
Internet  ------                       ---- httpd serving vhosts
                \                     /
                 \--- httpd (80)  ---/
                        proxy
                        mod_gzip

Have three httpd web servers, one listening to port 443 and forwarding
requests to a back-end server, one listening to port 80, forwarding 
requests to the _same_ back-end server, and using mod_gzip on the content.
Using more recent versions of Apache 1.3 and you can have mod_proxy proxy
requests using the same Host: header, although you lose the originating
IP address (there are some workarounds).

Shazam!  Per-TCP-port mod_gzip.

Cheers,
Glenn

On Thu, Oct 17, 2002 at 09:31:18AM -0700, Douglas Kirkland wrote:
> On Thursday 17 October 2002 08:14 am, you wrote:
> > Hi Douglas,
> >
> > > I do not think you understand the problem.
> > > I have over 4,000 server domain blocks that I am working with now.
> > > You want me to double this?
> >
> > Yes.
> >
> > > This would more then double my work.
> >
> > Not if each pair of these blocks would _include_ a configuration
> > file that has the same content as the block has now.
> >
> > You will have the same number of contents, only twice as much
> > include statements and twice as much blocks, which will then
> > only contain one (Port 80) or two (port 443) lines.
> >
> > And you would have 4000 include files.
> <heart attack>
> I still think you missed the point.  Our customer can edit their server 
> domain blocks.  Most of the time our customers are not the smartest fish in 
> the sea.  If they want they can upgrade apache themself, but all of them 
> choice not to go there.  If there is a problem with their server I would have 
> to go in and fix the problem and all I get from them is 'my server is not 
> working'.
> 
> </heart attack>
> 
> >
> > > Your idea would make me have to take care of over 8,000 server domain
> > > blocks.
> >
> > Yes, but only of 4000 pairs of identical content, just like you
> > have them already. I don't ask you to duplicate anything.
> >
> > Regards, Michael
> >
> I do not want to close access to the apache configuration file to our 
> clients.  Most of them would not care.  There still would be a few that would 
> want access or need access to the files.  I do know that we do setup our 
> apache configuration files differently then standard method.
> 
> Since mod_gzip is a added module for the web server it should be able to be 
> configured global in one place.  I should not have to think about this module 
> for evey server domain host that is setup.  Having a default exclude for port 
> 443 would solve the problem.  It should not take that much work to make the 
> module be able to exclude a port since it is already setup to exclude 'uri' 
> directories.  I could take a hack at it, but I have not work in 'C' and I do 
> not want to work with a non-standard module.  That would creates problems 
> down the road.
> 
> After a while the server domains for the port 443 will be different from the 
> server domain for port 80 stuff.  I just do not want to even start down that 
> road.   I am working on making my work easier so I can manage even more 
> server domains.  I would rather deal with the error message then have to work 
> with twice as many server domains.