Bug#233538: apache: a possible solution
Package: apache Version: 1.3.29.0.1-5 Severity: normal Followup-For: Bug #233538 Hi. I've seen on a RedHat installation that they use something like Include /etc/apache/conf.d/*.conf Instead of Include /etc/apache/conf.d This might be preferable for Debian as well. I have some custom packages having conffiles in /etc/apache/conf.d, and the default Apache config tries to include all those *.dpkg-* files and fails. What do you think? /etc/apache/conf.d is still pretty much new for Debian 1.3 packages. Zoran -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.23 Locale: LANG=C, LC_CTYPE=hr_HR Versions of packages apache depends on: ii apache-common 1.3.29.0.1-5 Support files for all Apache webse ii debconf 1.4.8Debian configuration management sy ii dpkg1.10.18 Package maintenance system for Deb ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdb4.24.2.52-9 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.6-6 XML parsing C library - runtime li ii libmagic1 4.07-2 File type determination library us ii libpam0g0.76-15 Pluggable Authentication Modules l ii logrotate 3.6.5-2 Log rotation utility ii mime-support3.24-1 MIME files 'mime.types' & 'mailcap ii perl [perl5]5.8.3-1 Larry Wall's Practical Extraction -- debconf information excluded
Bug#130883: A wonderful s/ex life!
Boost your confidence in the bedroom! Did you know that the normal cost for [EMAIL PROTECTED] is $20 per dose? We are running a hot special! TODAY its only an amazing $1.66 Find it here! http://medsfactory.com/gv/index.php?pid=evaph7482
Bug#130883: sugper viagrga
fabuklous! I took the only one pijll of Cialgs and that was such a GREAT weekend! All the girls at the party were just punch-drungk with my potentiagl I have fgcked all of them THREE times but my dgck WAS able to do some more! Cgalis - it`s COOL!!! The best weekend stuff I've ever trgied! Haven`t you tgried yet? DO IT at http://goandbuyit.com/sv/index.php?pid=eph2660
mod_autoindex StUdLyInDeXiNg
At some point Netgod forked mod_autoindex from upstream and added the
StudlyIndex option. That was fine until upstream added some features
and fixed some bugs. The plan is to turn the mod_autoindex in contrib
into a patch to the mod_autoindex distributed with apache.
Here is that patch. Comments welcomed (it's 17k, I must have missed
*something*).
--- build-tree-apache/apache_1.3.29/src/modules/standard/mod_autoindex.c
2003-12-09 14:47:37.0 -0500
+++ build-tree-apache/apache-contrib-1.0.8a/mod_autoindex/mod_autoindex.c
2004-02-19 13:16:31.0 -0500
@@ -63,6 +63,7 @@
* 3/23/93
*
* Adapted to Apache by rst.
+ * StudlyIndexing by Johnie Ingram <[EMAIL PROTECTED]>
*/
#include "httpd.h"
@@ -99,6 +100,7 @@ module MODULE_VAR_EXPORT autoindex_modul
#define FOLDERS_FIRST 512
#define TRACK_MODIFIED 1024
#define SORT_NOCASE 2048
+#define STUDLY_INDEXING 4096
#define K_PAD 1
#define K_NOPAD 0
@@ -163,6 +165,17 @@ typedef struct autoindex_config_struct {
array_header *ign_list;
array_header *hdr_list;
array_header *rdme_list;
+array_header *side_list;
+array_header *main_list;
+array_header *ftr_list;
+
+char *body_col;
+char *text_col;
+char *hdr_col;
+char *rdme_col;
+char *side_col;
+char *main_col;
+char *ftr_col;
} autoindex_config_rec;
@@ -196,11 +209,19 @@ static ap_inline int is_parent(const cha
* We include the DOCTYPE because we may be using features therefrom (i.e.,
* HEIGHT and WIDTH attributes on the icons if we're FancyIndexing).
*/
-static void emit_preamble(request_rec *r, char *title)
+static void emit_preamble(request_rec *r, char *title,
+ autoindex_config_rec *autoindex_conf)
{
-ap_rvputs(r, DOCTYPE_HTML_3_2,
+ap_rvputs(r, DOCTYPE_HTML_4_0T,
"\n \n Index of ", title,
- "\n \n \n", NULL);
+ "\n \n body_col ?: "#ff", "\" text=\"",
+ autoindex_conf->text_col ?: "#00", "\"", NULL);
+if (autoindex_conf->opts & STUDLY_INDEXING) {
+ ap_rvputs(r, " leftmargin=\"0\" topmargin=\"0\" \n "
+ "marginwidth=\"0\" marginheight=\"0\"", NULL);
+}
+ap_rputs(">\n\n", r);
}
static void push_item(array_header *arr, char *type, char *to, char *path,
@@ -340,6 +361,27 @@ static const char *add_readme(cmd_parms
return NULL;
}
+static const char *add_sidebar(cmd_parms *cmd, void *d, char *name)
+{
+push_item(((autoindex_config_rec *) d)->side_list, 0, NULL, cmd->path,
+ name);
+return NULL;
+}
+
+static const char *add_body(cmd_parms *cmd, void *d, char *name)
+{
+push_item(((autoindex_config_rec *) d)->main_list, 0, NULL, cmd->path,
+ name);
+return NULL;
+}
+
+static const char *add_footer(cmd_parms *cmd, void *d, char *name)
+{
+push_item(((autoindex_config_rec *) d)->ftr_list, 0, NULL, cmd->path,
+ name);
+return NULL;
+}
+
/* A legacy directive, FancyIndexing is superseded by the IndexOptions
* keyword. But for compatibility..
*/
@@ -385,6 +427,12 @@ static const char *add_opts(cmd_parms *c
if (!strcasecmp(w, "FancyIndexing")) {
option = FANCY_INDEXING;
}
+ else if (!strcasecmp(w, "StudlyIndexing")) {
+/* automatic FancyIndexing on, NameWidth=*, etc. */
+ option = STUDLY_INDEXING + FANCY_INDEXING
+ + ICONS_ARE_LINKS + SUPPRESS_DESC;
+d_cfg->name_adjust = K_ADJUST;
+ }
else if (!strcasecmp(w, "IconsAreLinks")) {
option = ICONS_ARE_LINKS;
}
@@ -406,16 +454,16 @@ static const char *add_opts(cmd_parms *c
else if (!strcasecmp(w, "SuppressColumnSorting")) {
option = SUPPRESS_COLSORT;
}
-else if (!strcasecmp(w, "FoldersFirst")) {
-option = FOLDERS_FIRST;
+ else if (!strcasecmp(w, "FoldersFirst")) {
+ option = FOLDERS_FIRST;
}
else if (!strcasecmp(w, "TrackModified")) {
-option = TRACK_MODIFIED;
+ option = TRACK_MODIFIED;
}
else if (!strcasecmp(w, "IgnoreCase")) {
-option = SORT_NOCASE;
+ option = SORT_NOCASE;
}
-else if (!strcasecmp(w, "None")) {
+ else if (!strcasecmp(w, "None")) {
if (action != '\0') {
return "Cannot combine '+' or '-' with 'None' keyword";
}
@@ -501,7 +549,49 @@ static const char *add_opts(cmd_parms *c
d_cfg->desc_adjust = K_NOADJUST;
}
}
-else {
+ else if (!strncasecmp(w, "BodyColor=", 10)) {
+ if (action == '-') {
+ return "Cannot combine '-' with BodyColor=#xx";
+ }
+ d_cfg->body_col = ap_pstrdup(d_cfg->desc_list->pool, &w[10]);
+ }
+ else if (!strncasecmp(w, "TextColor=", 10)) {
+ if (action == '-') {
+ return "Cannot combine '-' with TextC
Bug#233694: apache: mod_autoindex missing IndexOption IgnoreCase
On Fri, Feb 20, 2004 at 12:59:56AM +1100, Andrew Greig wrote: > After running 'strings' against mod_autoindex.so, then subsequently > examining the apache .orig.tar.gz, showed that the standard mod_autoindex > is not being used. Instead the mod_autoindex.c from apache-contrib-1.0.8a, > which lacks IgnoreCase, appears to be included. > > My questions: > - Why are contributed, undocumented modules being used instead of the > standard ones? > - Could the standard mod_autoindex be included instead? > - How can I list files case-insensitively with the current Debian apache? This is a decision that predates my involvement with Apache. From some archaelogical digging, mod_autoindex was modified by Johnie Ingram (the previous maintainer) to introduce StudlyIndexing. Now people may be using StudlyIndexing so we can't just arbitrarily switch back. The good news is that the IgnoreCase option doesn't seem to be a huge amount of work to add back to the forked version of mod_autoindex, and I intend to do so within the next week. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain
Bug#233694: apache: mod_autoindex missing IndexOption IgnoreCase
Package: apache Version: 1.3.29.0.1-3 Severity: normal The documentation for mod_autoindex mentions the IgnoreCase option to IndexOption, and explains if the option is enabled, filenames are sorted in a case-insensitive manner. However, using the option, for example: IndexOptions FancyIndexing NameWidth=* IgnoreCase gives an error like the following on apache restart: Syntax error on line 563 of /etc/apache/httpd.conf: IgnoreCase After running 'strings' against mod_autoindex.so, then subsequently examining the apache .orig.tar.gz, showed that the standard mod_autoindex is not being used. Instead the mod_autoindex.c from apache-contrib-1.0.8a, which lacks IgnoreCase, appears to be included. My questions: - Why are contributed, undocumented modules being used instead of the standard ones? - Could the standard mod_autoindex be included instead? - How can I list files case-insensitively with the current Debian apache? Cheers, Andrew Greig -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux shuttle 2.6.0-1-k7 #2 Sun Jan 11 17:06:46 EST 2004 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages apache depends on: ii apache-common 1.3.29.0.1-3 Support files for all Apache webse ii debconf 1.3.22 Debian configuration management sy ii dpkg1.10.18 Package maintenance system for Deb ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdb4.14.1.25-16Berkeley v4.1 Database Libraries [ ii libexpat1 1.95.6-6 XML parsing C library - runtime li ii libmagic1 4.07-2 File type determination library us ii libpam0g0.76-15 Pluggable Authentication Modules l ii logrotate 3.6.5-2 Log rotation utility ii mime-support3.24-1 MIME files 'mime.types' & 'mailcap ii perl [perl5]5.8.2-2 Larry Wall's Practical Extraction -- debconf information excluded
Re: apxs and LIBEXECDIR ?
Fabio Massimo Di Nitto <[EMAIL PROTECTED]> writes: > As I said the bug is pending. A fix has been already introduced to > avoid apache to stop upgrading. Another fix instead is on the way to > generate .info files from apxs (#228077) but it is still under > testing and it will not make it for this release Oh, great! Well that makes me happy then:-) Thanks! -- David N. Welton Consulting: http://www.dedasys.com/ Personal: http://www.dedasys.com/davidw/ Free Software: http://www.dedasys.com/freesoftware/ Apache Tcl: http://tcl.apache.org/
Re: apxs and LIBEXECDIR ?
On Thu, 19 Feb 2004, David N. Welton wrote: > Basically, yes. If I install a 3rd party module that uses apxs, it > will install in /usr/lib/apache/1.3, and presumably everything will be > working ok untill I try and upgrade and *bang*, my previously > functional installation is broken. > > I'm not sure what the 'solution' to this bug is, but if you consider > the number of bug reports that have arrived to date and do some > extrapolation to the number of stable users who will hit this on > upgrade, to me it seems evident that another solution is necessary. I > wish I were able to suggest something that would make everyone happy, > but I don't have all the world's answers, only some of them;-) As I said the bug is pending. A fix has been already introduced to avoid apache to stop upgrading. Another fix instead is on the way to generate .info files from apxs (#228077) but it is still under testing and it will not make it for this release Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Re: apxs and LIBEXECDIR ?
Fabio Massimo Di Nitto <[EMAIL PROTECTED]> writes: > Hi David, > sorry for the late reply but i didn't notice this mail until now. No problem. > > Another thought that crossed my mind. apxs -q LIBEXECDIR is where > > automated installers might want to put modules, right? > Yes. > > At least if they are using apxs as a guide. > That's correct. > > Another reason why just dying because of modules in that directory > > is a bad idea, IMO... > sorry but i don't understand.. related to what? > If you are talking about #226833 it is pending right now. Basically, yes. If I install a 3rd party module that uses apxs, it will install in /usr/lib/apache/1.3, and presumably everything will be working ok untill I try and upgrade and *bang*, my previously functional installation is broken. I'm not sure what the 'solution' to this bug is, but if you consider the number of bug reports that have arrived to date and do some extrapolation to the number of stable users who will hit this on upgrade, to me it seems evident that another solution is necessary. I wish I were able to suggest something that would make everyone happy, but I don't have all the world's answers, only some of them;-) -- David N. Welton Consulting: http://www.dedasys.com/ Personal: http://www.dedasys.com/davidw/ Free Software: http://www.dedasys.com/freesoftware/ Apache Tcl: http://tcl.apache.org/
Bug#231240: marked as done (Didn't install until I did manual /etc/init.d/apache stop... apache start)
Your message dated Thu, 19 Feb 2004 10:52:41 +0100 (CET) with message-id <[EMAIL PROTECTED]> and subject line Bug#231240: Didn't install until I did manual /etc/init.d/apache stop... apache start has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 5 Feb 2004 10:38:59 + >From [EMAIL PROTECTED] Thu Feb 05 02:38:59 2004 Return-path: <[EMAIL PROTECTED]> Received: from hestia.its.rmit.edu.au [131.170.1.10] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AoguQ-0002QI-00; Thu, 05 Feb 2004 02:38:59 -0800 Received: from iii.rmit.edu.au (ns.iii.rmit.edu.au [131.170.185.10]) by hestia.its.rmit.edu.au (8.12.10/8.12.10/hestia) with ESMTP id i15AcM8v004891 for <[EMAIL PROTECTED]>; Thu, 5 Feb 2004 21:38:24 +1100 (EST) Received: from immersive20.iii.rmit.edu.au (Immersive20.iii.rmit.edu.au [131.170.185.104]) by iii.rmit.edu.au (8.12.11/8.12.0) with ESMTP id i15AcNSc487211 for <[EMAIL PROTECTED]>; Thu, 5 Feb 2004 21:38:23 +1100 (AEDT) Received: by immersive20.iii.rmit.edu.au (Postfix, from userid 1000) id 13477C03070; Thu, 5 Feb 2004 21:38:18 +1100 (EST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: ADFH <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: Didn't install until I did manual /etc/init.d/apache stop... apache start X-Mailer: reportbug 2.42 Date: Thu, 05 Feb 2004 21:38:18 +1100 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_02_01 X-Spam-Level: Package: apache Version: 1.3.29.0.1-5 Severity: normal Upgrading to latest unstable release, and Apache wouldn't install, complaining about getting an error from the init.d script trying to start. I manually ran the init.d script to start and stop apache, and then reran dist-upgrade, and it happily installed. Not sure what's happening. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.18-xfs-1.1 Locale: LANG=C, LC_CTYPE=C Versions of packages apache depends on: ii apache-common 1.3.29.0.1-5 Support files for all Apache webse ii debconf 1.4.8Debian configuration management sy ii dpkg1.10.18 Package maintenance system for Deb ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdb4.24.2.52-9 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.6-6 XML parsing C library - runtime li ii libmagic1 4.07-2 File type determination library us ii libpam0g0.76-15 Pluggable Authentication Modules l ii logrotate 3.6.5-2 Log rotation utility ii mime-support3.24-1 MIME files 'mime.types' & 'mailcap ii perl [perl5]5.8.3-1 Larry Wall's Practical Extraction -- debconf information excluded --- Received: (at 231240-done) by bugs.debian.org; 19 Feb 2004 09:52:44 + >From [EMAIL PROTECTED] Thu Feb 19 01:52:44 2004 Return-path: <[EMAIL PROTECTED]> Received: from port5.ds1-sby.adsl.cybercity.dk (trider-g7.fabbione.net) [212.242.169.198] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AtkrM-00060C-00; Thu, 19 Feb 2004 01:52:44 -0800 Received: from trider-g7.ext.fabbione.net (port5.ds1-sby.adsl.cybercity.dk [212.242.169.198]) by trider-g7.fabbione.net (Postfix) with ESMTP id 4CC7916; Thu, 19 Feb 2004 10:52:41 +0100 (CET) Date: Thu, 19 Feb 2004 10:52:41 +0100 (CET) From: Fabio Massimo Di Nitto <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] To: ADFH <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: Bug#231240: Didn't install until I did manual /etc/init.d/apache stop... apache start In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_18 (1.212-200
Re: apxs and LIBEXECDIR ?
Hi David, sorry for the late reply but i didn't notice this mail until now. On Tue, 3 Feb 2004, David N. Welton wrote: > > Another thought that crossed my mind. apxs -q LIBEXECDIR is where > automated installers might want to put modules, right? Yes. > At least if they are using apxs as a guide. That's correct. > Another reason why just dying because of modules in that directory is a > bad idea, IMO... sorry but i don't understand.. related to what? If you are talking about #226833 it is pending right now. Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Bug#231240: Didn't install until I did manual /etc/init.d/apache stop... apache start
> From which version of apache were you upgrading? Please send the log of > the upgrade. Would have been one of: -rw-r--r--+ 1 root root 353130 Nov 5 2002 apache_1.3.26-0woody3_i386.deb -rw-r--r--+ 1 root root 369808 Jun 27 2003 apache_1.3.27.0-2_i386.deb -rw-r--r--+ 1 root root 364634 Dec 18 02:17 apache_1.3.29.0.1-3_i386.deb (from /var/cache/apt/archives - not sure - occasionally I get to do dist-upgrade -dyu, but don't get around to installing packages and then end up updating and dist-upgrading again and skipping some cached packages. Fairly safe to say it was probably 1.3.29.0.1-3) Sorry I couldn't be more specific.. Either way - have upgraded several boxes since - so perhaps it was a transient file system error on the box in question. Sorry to trouble you. Regards, ADFH
