Received: (qmail 24348 invoked by uid 501); 14 Aug 2000 18:36:34 -0000 Message-Id: <20000814183634.24347.qmail@locus.apache.org> Date: 14 Aug 2000 18:36:34 -0000 From: Jeffrey Perry Reply-To: jperry@vistasource.com To: submit@bugz.apache.org Subject: [warn] [Mon Aug 14 12:47:43 2000] Loaded DSO modules/mod_aaproxy.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) X-Send-Pr-Version: 3.110 >Number: 6417 >Category: documentation >Synopsis: [warn] [Mon Aug 14 12:47:43 2000] Loaded DSO modules/mod_aaproxy.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Mon Aug 14 11:40:00 PDT 2000 >Closed-Date: Sun Sep 17 18:59:16 PDT 2000 >Last-Modified: Sun Sep 17 18:59:16 PDT 2000 >Originator: jperry@vistasource.com >Release: 1.3.12 >Organization: >Environment: Linux RedHat 6.2 >Description: I could find NO information on what the EAPI is on the Apache websites in either the FAQ or the documentation. I finally tracked down a paragraph on the ApacheWeek website. I think the docs and FAQ should be updated to cover what it is and how to use it (since it seems to be included in 1.3.12) The module which is giving me problems is my own. I tried compiling it standalone (which has always worked) and adding -DEAPI to the compile line. The same error occurs. I am sure there must be a simple explanation but numerous searches online have turned up only the same question I am asking with no answers on how to fix the build or if it even needs fixing. The module appears to function fine. Do I need to fix this warning? Is there truel;y a risk of it crashing? What specifically has changed in the API? There might be new featues of use to me. Even is the following. I am running the copy of Apache 1.3.12 which Redhat installed. I fetched the source code from www.apache.org. and grepping turns up no references to EAPI - please point me at the file(s) in question. Thanks in advance for your assistance. >How-To-Repeat: >Fix: See above - document whether this warning is harmless and document the new EAPI or add pointers to the info on the website which I have somehow not managed to find. Thanks! >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: slive State-Changed-When: Sun Sep 17 18:59:16 PDT 2000 State-Changed-Why: EAPI is actually contained in a third-party patch (see http://www.modssl.org/) and is not distributed with Apache. Therefore, I believe you should be contacting Redhat about their lack of documentation, since they have patched Apache. Perhaps a FAQ entry might be justified, but there is no way that we can document third-party patches. Thanks for using Apache! >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]