I tried what you said. I compiled with --enable-shared=all. Also for what ever reason in my copy of apache 2.0.45, when you run ./ configure --help,
I don't see the "--enable-shared" option in the list of possible options.
I still cannot get it work loaded at the end of the httpd.conf file. But it works fine only when loaded first as shown below.
For what it is worth!!
Sri Amudhanar
Bill Conlon wrote:
I had this issue with Redhat9/apache 2.0.46 The answer was ./ configure --enable-shared=allUpdate: Magic module didn't work for me. I disabled the mod_mime_magic.so line and I was still getting the whole XML document back. But I was able to get my wapache2.so work by doing the following (Linux) 1. Compiled and installed apache 2.0.45 in /usr/local/apache2 2. Mioved the Witango lines to the top of the "/usr/local/apache2/conf/httpd.conf" file: # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. # # Example: # LoadModule foo_module modules/mod_foo.so # LoadModule WitangoModule "/usr/local/apache2/modules/wapache2.so" WitangoModule wapache2.so LoadModule access_module modules/mod_access.so LoadModule auth_module modules/mod_auth.so LoadModule auth_anon_module modules/mod_auth_anon.so LoadModule auth_dbm_module modules/mod_auth_dbm.so LoadModule auth_digest_module modules/mod_auth_digest.so LoadModule ext_filter_module modules/mod_ext_filter.so LoadModule include_module modules/mod_include.so ---blah blah---- I had loaded it in the end as usual in Tango2000. But load order seems to matter, at least in this case and Witango DSO must load first. Hope this helps some one. Sri Amduhanar Maxys Corporation Witango Reseller Witango Development, Support and Training. 703 729 0600 [EMAIL PROTECTED] Sri Amudhanar wrote:Bingo! That is one my problems. Thanks for identifying it! But, shouldn't we be trying to solve the problem by adding the definition to the magic file instead of disabling the xml part? I am going to look into replicating your success, but I was wondering if Witango Support will be able to provide a snippet for the magic file Sri John McGowan wrote:Just thought I'd post this little bit of information to help anybody who goes to run Witango on Apache. If you compile Apache yourself with all modules, you will have problems with Witango. This is because of the mod_mime_magic module. The mime magic module looks at files contents (not just the extension) and messes with the content type. This causes tht wapache2 module to not do it's job, and instead the web server just servs up the Witango XML files. So, to save yourself some time, make sure you disable at least the xml part of the "magic" file, or the entire magic module in httpd.conf Hope this helps someone. /John ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.tafBill Conlon To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306 office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
