httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Sawant" <>
Subject Enabing Rewrite as a DSO throws DEAPI warning message
Date Fri, 16 Aug 2002 09:50:38 GMT

i have apache 1.3.26 with mod ssl.

when i enable mod_rewrite as a DSO , the following warning message is thrown
at startup.

[Fri Aug 16 08:57:11 2002] [warn] Loaded DSO libexec/ uses
plain Apache 1.3 API, this module might crash under EAPI! (please recompile
it with -DEAPI)
Apache/1.3.23 mod_ssl/2.8.6 (Pass Phrase Dialog)

but it seems to be harmless.

following is said
"When you install mod_ssl... it rewrites your entire Apache source code
to make it work the way the mod_ssl folks want it to and they install
something called the EAPI which does nothing more than add a
few more 'hooks' into the Apache engine. The mod_ssl folks need
a 'hook' at the 'connection' level so they can get ahold of the socket
at the lowest level and do the encryption.

After the patches are applied the mod_ssl hacks are too dumb to
know if a module actually uses EAPI or not so they simply assume
that all of them do and put out that 'warning'.

If you write a module that DEPENDS on EAPI and you forget to
compile it with -DEAPI then yes... it might crash... but non-EAPI
modules will not and the warning is meaningless.

You can just IGNORE this warning, or recompile with -DEAPI.
but it doesn't make any difference if you do."

Please can anyone throw some light on the following

1) How to figure out if a module uses EAPI?
2) what is DEAPI?


Milind Sawant
Web Administrator (Apollo)

+0041 1 288 4675

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message