httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Bloom" <...@covalent.net>
Subject RE: Using Apache 1.3 modules with 2.0 was Re: Please help kill httpd-2.0 bugs...
Date Wed, 27 Feb 2002 17:03:52 GMT
> On Wed, Feb 27, 2002 at 04:44:03PM +0000, Thom May wrote:
> > * Justin Erenkrantz (jerenkrantz@ebuilt.com) wrote :
> > > --
> > > >Number:         9952
> > > >Category:       mod_jserv
> > > >Synopsis:       Cannot load tomcat connection module
> > > >Arrival-Date:   Mon Feb 25 07:10:01 PST 2002
> > > >Release:        2.0.32
> >
> > In regards to Pier's message about 1.3 jserv bugs being reassigned
to
> > Jakarta, should this one go to?
> 
> Sounds like someone is using an Apache 1.3 module with 2.0.  I'm
> closing this bug with that note and mentioning that further
> Tomcat bugs should be filed with Jakarta's bug system.
> 
> However, that brings up a point:
> 
> Can we detect when a 1.3 module will be used with 2.0?  One of my
> housemates was trying to install the PHP 1.3 module with 2.0.32 on
> Win32 last night.  It just said as this bug does too:
> 
> Cannot load E:/apache/Apache2/modules/ApacheModuleJServ.dll into
server:
> The specified module could not be found.
> 
> Can we detect and report an suitable error message in this
> case?  -- justin

Yeah, that's actually trivial.  The module structure has a key that is
the Apache version number.  Look at MODULE_MAGIC_COOKIE.  Just do a
quick comparison when we load the module, and output a valid error.

Ryan



Mime
View raw message