Processed: upstream
Processing commands for [EMAIL PROTECTED]: tags 242543 - help Bug#242543: apache: PATH_INFO not set for !--#include virtual=page.html/path?query -- Tags were: help Tags removed: help forwarded 242543 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31214 Bug#242543: apache: PATH_INFO not set for !--#include virtual=page.html/path?query -- Noted your statement that Bug has been forwarded to http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31214. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: mod-mono has screwed up my apache
On Tue, 14 Sep 2004, Mike McKay wrote: Hi, I am getting the following error whenever I try and do pretty much anything (installing Squirrelmail) via apt now: Error: libmod_mono.so does not have a corresponding .info file. The above errors might cause apache to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Maling List debian-apache@lists.debian.org if in doubt on how to proceed Error: libmod_mono.so does not have a corresponding .info file. The above errors might cause apache-perl to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Maling List debian-apache@lists.debian.org if in doubt on how to proceed I followed the instructions for installing mono from source (again, mod-mono is from source, not from apt) which basically directed me to add the following to my httpd.conf: [SNIP] I have had this problem for a while now, but now I need to install squirrelmail which apparently requires clean apache upgrades. The error message recommended me getting in contact if I don't know how to fix it - so here I am. I think I need to generate a .info file, but I the semantics of such a thing are beyond me. Hi, please install apache-dev and read /usr/share/doc/apache-dev/REAMDE.modules It will explain to you what a .info file is and how to create a proper one for your apache installation. The above is a warning to prevent external module to mangle apache configuration (given that the user is using standard debian tools for it). Nothing to be scared about. it's one line and one file :-) Fabio -- user fajita: step one fajita Whatever the problem, step one is always to look in the error log. user fajita: step two fajita When in danger or in doubt, step two is to scream and shout.
Re: mod-mono has screwed up my apache
Fabio Massimo Di Nitto wrote: On Tue, 14 Sep 2004, Mike McKay wrote: Hi, I am getting the following error whenever I try and do pretty much anything (installing Squirrelmail) via apt now: Error: libmod_mono.so does not have a corresponding .info file. The above errors might cause apache to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Maling List debian-apache@lists.debian.org if in doubt on how to proceed Error: libmod_mono.so does not have a corresponding .info file. The above errors might cause apache-perl to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Maling List debian-apache@lists.debian.org if in doubt on how to proceed I followed the instructions for installing mono from source (again, mod-mono is from source, not from apt) which basically directed me to add the following to my httpd.conf: [SNIP] I have had this problem for a while now, but now I need to install squirrelmail which apparently requires clean apache upgrades. The error message recommended me getting in contact if I don't know how to fix it - so here I am. I think I need to generate a .info file, but I the semantics of such a thing are beyond me. Hi, please install apache-dev and read /usr/share/doc/apache-dev/REAMDE.modules It will explain to you what a .info file is and how to create a proper one for your apache installation. The above is a warning to prevent external module to mangle apache configuration (given that the user is using standard debian tools for it). Nothing to be scared about. it's one line and one file :-) At the danger of giving the next guy a fish instead of showing him how to fish, as you kindly did, here is the lazy man's answer: Create file: /usr/lib/apache/1.3/500mod_mono.info with contents: LoadModule: mono_module /usr/lib/apache/1.3/libmod_mono.so Cheers! Mike
Informations for packaging apache(2) third party modules
Hi everybody, I'm working on packaging a new apache module for apache/apache2 (www.suphp.org), and I try to find the best way for my postinsts/prerms scripts. I found the README.modules in apache-dev, but nothing for apache2-dev. So I looked at some other packages and saw that often they simply a2enmod without asking the user... AW, is there a place where I can find informations on packaging tools with dependendies on apache like apache modules. If there isn't such a place I would suggest to set up a simple page or wiki (I can do this) and add a link to Packaging section on Developers' Corner at www.debian.org. Regards, -- Emmanuel LACOUR - [EMAIL PROTECTED]
Re: Informations for packaging apache(2) third party modules
* Emmanuel Lacour ([EMAIL PROTECTED]) wrote : Hi everybody, I'm working on packaging a new apache module for apache/apache2 (www.suphp.org), and I try to find the best way for my postinsts/prerms scripts. I found the README.modules in apache-dev, but nothing for apache2-dev. So I looked at some other packages and saw that often they simply a2enmod without asking the user... AW, is there a place where I can find informations on packaging tools with dependendies on apache like apache modules. If there isn't such a place I would suggest to set up a simple page or wiki (I can do this) and add a link to Packaging section on Developers' Corner at www.debian.org. libapache2-mod-macro is pretty much the simplest possible case for an apache2 module. get the source for that, and run with it. -Thom -- That sounds like a lot of work... Can we out source? The Revolution will not be outsourced! (Slick/Monique - Sinfest)
Bug#267477: Apache2 and SSL Quick Hints
Here is a rough outline of how to get Apache2 SSL working. I agree that the package could be more SSL friendly out of the box. I came here to file a bug myself ;-). Steps: 1. Have Apache working without SSL! 2. Generate your SSLCertificateFile and SSLCertificateKeyFile files. I used the newcert-ca.sh script at http://www.openssl.org/contrib/ . If you go this route be sure to read the script before you start running it so that you understand what you are doing. You will run it one time to create a CA and a second time calling that CA to create a the files for your server. 3. Copy the .key and .cert over to the /etc/apache2/ssl/ directory so that they are easy to get to. 4. Copy your sites-available/default file and call it default-ssl. ***Including this file already set up is something that the APACHE2 .deb could be doing at install time.*** 5. Edit your new default-ssl as follows. The first two lines you will just edit what is there. The stuff inside the # SSL STUFF + bars will be inserted after the VirtualHost *:443 line: NameVirtualHost *:443 VirtualHost *:443 # SSL STUFF (START) SSLEngine on SSLCertificateFile /etc/apache2/ssl/server_cert_name_httpsd.cert SSLCertificateKeyFile /etc/apache2/ssl/server_key_name_httpsd.key # see http://httpd.apache.org/docs-2.0/ssl/ssl_howto.html for the meaning of below. # The following enables only the seven strongest ciphers. SSLProtocol all SSLCipherSuite HIGH:MEDIUM # SSL STUFF (END) +++ 6. Run a2enmod and make sure that ssl is enabled. 7. Make sure the ports.conf line contains both a Listen 80 and a Listen 443 line. 8. Test your setup by running apache2 -D SSL -S. The results should look something like these below: littleguy:/etc/apache2/sites-enabled# apache2 -D SSL -S apache2: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName VirtualHost configuration: wildcard NameVirtualHosts and _default_ servers: *:443 is a NameVirtualHost default server 127.0.0.1 (/etc/apache2/sites-enabled/default-ssl:2) port 443 namevhost 127.0.0.1 (/etc/apache2/sites-enabled/default-ssl:2) *:80 is a NameVirtualHost default server 127.0.0.1 (/etc/apache2/sites-enabled/default:2) port 80 namevhost 127.0.0.1 (/etc/apache2/sites-enabled/default:2) Syntax OK 9. /etc/inid.d/apache2 restart and then go test your SSL (and nonSSL) pages. Debian Apache Maintainers -- Could y'all include at least a sample default-ssl file and some terse documentation in the README? Thanks, Sam
mod-mono has screwed up my apache
Hi, I am getting the following error whenever I try and do pretty much anything (installing Squirrelmail) via apt now: Error: libmod_mono.so does not have a corresponding .info file. The above errors might cause apache to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Maling List debian-apache@lists.debian.org if in doubt on how to proceed Error: libmod_mono.so does not have a corresponding .info file. The above errors might cause apache-perl to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Maling List debian-apache@lists.debian.org if in doubt on how to proceed I followed the instructions for installing mono from source (again, mod-mono is from source, not from apt) which basically directed me to add the following to my httpd.conf: # Allow http put (such as Netscape Gold's publish feature) # Use htpasswd to generate /etc/apache/passwd. # You must unremark these two lines at the top of this file as well: #LoadModule put_modulemodules/mod_put.so LoadModule mono_module/usr/lib/apache/1.3/libmod_mono.so #AddModule mod_put.c AddModule mod_mono.c Alias /mono /var/www/mono MonoApplications /mono:/var/www/mono/ MonoPath /var/www/mono/bin/ MonoDocumentRootDir /var/www/mono/bin/ Directory /var/www/mono/ SetHandler mono Options Indexes FollowSymLinks IfModule mod_dir.c DirectoryIndex index.aspx index.html /IfModule /Directory I have had this problem for a while now, but now I need to install squirrelmail which apparently requires clean apache upgrades. The error message recommended me getting in contact if I don't know how to fix it - so here I am. I think I need to generate a .info file, but I the semantics of such a thing are beyond me. I am not on this mailing list so please CC me directly. Thanks, in advance, Mike PS I am on Debian Testing
