Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 29853 invoked by uid 500); 16 Aug 2002 09:42:30 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 29842 invoked from network); 16 Aug 2002 09:42:29 -0000 Received: from mail.skandiafinanz.ch (HELO sbsex1.skandiabank.intra) (212.23.235.139) by daedalus.apache.org with SMTP; 16 Aug 2002 09:42:29 -0000 Received: through eSafe SMTP Relay 1029232205; Fri Aug 16 11:44:11 2002 Received: from tcs2 (172.25.19.83 [172.25.19.83]) by sbsex1.skandiabank.intra with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id Q59FFMX6; Fri, 16 Aug 2002 11:42:53 +0200 From: "Milind Sawant" To: "Apache" Subject: Enabing Rewrite as a DSO throws DEAPI warning message Date: Fri, 16 Aug 2002 11:50:38 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi 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/mod_rewrite.so 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? thanks Milind Sawant Web Administrator (Apollo) TCS +0041 1 288 4675 --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org