Re: What is the reason of using apache2.conf instead of httpd.conf?
On Tue, Apr 12, 2005 at 01:57:28PM +0200, Alexis Sukrieh wrote: * Daniel Stone ([EMAIL PROTECTED]) disait : httpd.conf is supported as well. The idea was that apache2.conf would be a tiny, minimal file that users never needed to change, while httpd.conf would remain for user customisations. This is because people would often customise some of the more ridiculous settings in httpd.conf, and then get annoyed when dpkg prompted them to ask what to do about it when it changed upstream. At least, speaking as the guy who made this change, that was my motivation. Then, in a way, httpd.conf is a kind of .local conffile now? httpd.conf is never modified by the package, and is intended for customisation by the administrator (or the packages he installs by hand; non-Debian-specific install scripts will tend to want to eat httpd.conf instead of using conf.d) only. signature.asc Description: Digital signature
Re: What is the reason of using apache2.conf instead of httpd.conf?
On Mon, Apr 11, 2005 at 04:23:47PM +0100, Lengyel Róbert wrote: I don't know why was it necessary to change the configuration file from httpd.conf to apache2.conf in the apache2 debian package. It annoys me very much. I wonder if there is a reason behind this. Does anyone know it? httpd.conf is supported as well. The idea was that apache2.conf would be a tiny, minimal file that users never needed to change, while httpd.conf would remain for user customisations. This is because people would often customise some of the more ridiculous settings in httpd.conf, and then get annoyed when dpkg prompted them to ask what to do about it when it changed upstream. At least, speaking as the guy who made this change, that was my motivation. signature.asc Description: Digital signature
Bug#303228: apache2-common: a2(en|dis)(mod|site) scripts should make apache2 reload
tags 303228 = wontfix thanks mate On Wed, Apr 06, 2005 at 08:46:02AM +0200, Sebastian Hegler wrote: Daniel Stone wrote: Also, think of this case: you enable a module such as proxy, which sets up proxying, but you need to configure it first so it's not an open proxy, or whatever. This is counter-intuitive, too, IMHO. You would only want to enable something that is already configured. Thanks for telling me how I use my computer ... but that's not how it happens. A lot of HOWTOs also describe first enabling and then configuring the module. How about the following behavior: 1. Create symlink in enabled dir. 2. Run apache2ctl configtest to do basic syntax checking. 3. If 2) fails, remove symlink created in 1), complain, exit. If 2) is successful, restart apache2. No. The current behaviour is fine. signature.asc Description: Digital signature
Bug#303228: apache2-common: a2(en|dis)(mod|site) scripts should make apache2 reload
On Tue, Apr 05, 2005 at 05:49:44PM +0200, [EMAIL PROTECTED] wrote: On Tue, Apr 05, 2005 at 04:11:55PM +0200, Sebastian Hegler wrote: the scripts a2(en|dis)(mod|site) should make apache2 reload instead of writing a message, stating that you should do it yourself. I find this pretty counter-intuitive and suggest this behaviour to be changed. Yes, but if you need to en/deisable more than one module your intuitive behaviour gets rathe anoying. Please leave it as it is. Also, think of this case: you enable a module such as proxy, which sets up proxying, but you need to configure it first so it's not an open proxy, or whatever. signature.asc Description: Digital signature
Bug#267477: such basic things need to be USERFRIENDLY
On Mon, Mar 07, 2005 at 11:14:04AM +0100, Eduard Bloch wrote: Come on people, is that really THAT COMPLICATED to add a simple guide to new admins to enable such base functionality like SSL? Is this Debian or LFS or why T.F. is a such basic thing so complicated? Even Gentoo guys managed to solve it in a sane manner, you get correct docs and most things are already preconfigured. For Debian, there is NOTHING in README.Debian (or is hidden in some obscure other file that is not easy to find). Fsck that. Even howtos like http://www.ianmiller.net/article.php?id=13 do not work out of the box [1]. Look at Exim4 maintainers. Understandable guides to enable things like TLS. Simple. Userfriendly. Tested for fresh installations, no falls and traps. The stuff for SSL setup in Apache2 packages makes me really pissed. Eduard, While I admire your commitment, the abuse leaves a little to be desired, and is possibly the worst way to motivate anyone to do anything. I hope your next comment on this bug is a patch. signature.asc Description: Digital signature
Bug#263101: FTBFS on GNU/k*BSD (config.* update)
tags 263101 pending
thanks mate
Robert,
I already merged something quite like this into my tla archive, and it's
pending upload (waiting for something more dramatic to change, I
suppose).
:) d
On Tue, Aug 03, 2004 at 01:54:27AM +0200, Robert Millan wrote:
Hi!
Please could you update config.{guess,sub}? This will fix FTBFS on GNU/k*BSD.
Thanks.
--- old/apache2-2.0.50/debian/rules 2004-08-03 01:51:58.0 +0200
+++ apache2-2.0.50/debian/rules 2004-08-03 00:14:20.0 +0200
@@ -85,6 +85,10 @@
configure: $(STAMP_DIR)/configure
$(STAMP_DIR)/configure: $(STAMP_DIR)/source.make
+ for i in build srclib/pcre srclib/apr/build srclib/apr-util/build \
+ srclib/apr-util/xml/expat/conftools ; do \
+ cp /usr/share/misc/config.* $(B)/$$i ; \
+ done
cd $(B) ./buildconf
touch $@
@@ -115,7 +119,7 @@
for i in $(FIRSTMPM) $(OTHERMPMS); do \
rm -f debian/apache2-mpm-$$i.postinst ;\
rm -f debian/apache2-mpm-$$i.init.d ;\
-done
+ done
rm -f debian/apache2-mpm-prefork.init.d
dh_clean
--
Daniel Stone[EMAIL PROTECTED]
Debian: the universal operating system http://www.debian.org
signature.asc
Description: Digital signature
Re: Apache configuration for virtual mass-hosting
On Wed, Jul 14, 2004 at 02:40:15PM +0200, Piotr Roszatycki wrote: I'd like to contribute to Debian my Apache 1.3 configuration which provides the easiest way to using virtual servers. The virtual server is created with proper mkdir command. The schema is very simple: /var/www/vhosts/name-port for document root and /var/log/apache/vhosts/name-port for log files. There is no VirtualHost sections in httpd.conf. Whole magic is done through mod_rewrite. See http://people.debian.org/~dexter/apacheconf/ and have a good fun. Heh. This sounds like what vhost-base provides, to some degree. -- Daniel Stone[EMAIL PROTECTED] Debian: the universal operating system http://www.debian.org signature.asc Description: Digital signature
Re: Apache configuration for virtual mass-hosting
On Wed, Jul 14, 2004 at 06:12:00PM +0100, Thom May wrote: * Daniel Stone ([EMAIL PROTECTED]) wrote : On Wed, Jul 14, 2004 at 02:40:15PM +0200, Piotr Roszatycki wrote: I'd like to contribute to Debian my Apache 1.3 configuration which provides the easiest way to using virtual servers. The virtual server is created with proper mkdir command. The schema is very simple: /var/www/vhosts/name-port for document root and /var/log/apache/vhosts/name-port for log files. There is no VirtualHost sections in httpd.conf. Whole magic is done through mod_rewrite. See http://people.debian.org/~dexter/apacheconf/ and have a good fun. Heh. This sounds like what vhost-base provides, to some degree. yes. CRACK! ;-D It just needs some time for someone to do a rewrite and give it Python love ... -- Daniel Stone[EMAIL PROTECTED] Debian: the universal operating system http://www.debian.org signature.asc Description: Digital signature
[EMAIL PROTECTED]: apache2 deb port]
I think it's because of the mixing of VirtualHost and NameVirtualHost; I'll ask the list about it. :) d - Forwarded message from Luke Worthy [EMAIL PROTECTED] - From: Luke Worthy [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: apache2 deb port Date: Thu, 8 Apr 2004 12:51:46 +1000 Message-Id: [EMAIL PROTECTED] I saw your name in the README.Debian with respect to problems with vhost-base for apache2 and thought you might be able to help me :)maybe. I have been setting up a server (debain woody with apache2 from backports.org) and am having some virtual host issues. I've got 2 sites configured so far, the coldfusionmx admin page, and the vhost alias for all our web sites, they are below: cfmx admin: VirtualHost 192.168.0.143 ServerAdmin [EMAIL PROTECTED] VirtualDocumentRoot /etc/htdocs/ ServerName defiant.solman CustomLog /var/log/cfaccess.log combined /VirtualHost Directory /etc/htdocs Options -Indexes MultiViews FollowSymLinks AllowOverride None Order allow,deny Allow from 192.168.0 /Directory * normal websites: NameVirtualHost * Directory /webpages/clientroot/ Options -Indexes MultiViews FollowSymLinks AllowOverride None Order allow,deny Allow from all /Directory UseCanonicalNameOff VirtualHost * ServerName * VirtualDocumentRoot /webpages/clientroot/%2.1/%2.2/%0 DirectoryIndex default.cfm default.htm index.cfm index.htm index.html ErrorDocument 404 /404.cfm /VirtualHost So I need to understand, whenever I run just the normal websites - works no problem, but when I add in the definition for the admin page, the server can't seem to serve the website pages anymore. The error log says: Directory index forbidden by rule: /etc/htdocs/ Which is insane, because it shouldn't use the DocRoot of the first non-vhost definition as the doc root - I would think it should use the vhosts first, and if then it's not found do the non-vhostsor maybe something else.point is - it's not working and I really need some help - if either you or anyone else you know that I can email, any help would be appreciated :) Luke - End forwarded message - -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne signature.asc Description: Digital signature
Re: email list
On Wed, Mar 31, 2004 at 11:01:33AM +, Ali SOOK wrote: Would you please be kind to delete those records: http://lists.debian.org/debian-apache/2004/debian-apache-200403/msg00311.html http://lists.debian.org/debian-apache/2004/debian-apache-200403/threads.html You spam, you get what you deserve. Go away. -- Daniel Stone[EMAIL PROTECTED] Debian: the universal operating system http://www.debian.org
Bug#234591: apache2-common: Confusing SSL configuration
On Sun, Mar 14, 2004 at 11:54:12PM -0800, Chris Stork wrote: I tried to configure apache2 with SSL (in order to run a subversion repository) and it was unclear to me what's the preferred way to configure SSL access. I found four sources of SSL-related information on my unstable box: - /usr/share/doc/apache2-common/README-SSL - /usr/share/doc/apache2/examples/ssl.conf.gz - the program apache2-ssl-certificate and its output (I assume) in /etc/apache2/ssl/ - /etc/apache2/mods-available/ssl.conf None of them seem to be aware of the other, as can be derived from where they place their files, e.g., for certificates we have: - README-SSL:/etc/apache2/sites/SERVERNAME-ssl.*/ As the author of this file, I'd advise you to ignore it. It's a hangover from the vhost-base days. Cheers! :) d -- Daniel Stone[EMAIL PROTECTED] Debian: the universal operating system http://www.debian.org pgpgO6IdbudYC.pgp Description: PGP signature
Bug#234552: apache2-mpm-perchild: extremely slow startup at boot time
On Tue, Feb 24, 2004 at 09:41:11AM -0500, Charles Fry wrote: Every time my webserver reboots, apache2-mpm-perchild takes around 3 minutes to startup. For a long time I thought it was hanging, and would simply kill it, but today I realized that after waiting long enough it would eventually start (at least some of the time). I realize that this is an experimental release, but there should be no difficulty in starting apache at boot time, inasmuch as it starts perfectly fine using the init.d scripts. This is because your DNS is broken. -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne pgpESGJtZPoT0.pgp Description: PGP signature
Bug#234552: apache2-mpm-perchild: extremely slow startup at boot time
On Tue, Feb 24, 2004 at 10:02:00AM -0500, Charles Fry wrote: Every time my webserver reboots, apache2-mpm-perchild takes around 3 minutes to startup. For a long time I thought it was hanging, and would simply kill it, but today I realized that after waiting long enough it would eventually start (at least some of the time). I realize that this is an experimental release, but there should be no difficulty in starting apache at boot time, inasmuch as it starts perfectly fine using the init.d scripts. This is because your DNS is broken. In what way do you supsect that my DNS is broken? I am running under usermodelinux, so that may effect the order that certain things happen. It's trying to look up your hostname, and the resolution is timing out. It's an FAQ. Hitting up Google before you submit bugs saves us all time. -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne pgpSwYItiZ1CY.pgp Description: PGP signature
Bug#225809: apache2: can -dev packages depend on libdb-dev instead of libdb4.1-dev?
On Fri, Jan 02, 2004 at 02:12:39PM +, Colin Watson wrote: On Thu, Jan 01, 2004 at 07:57:35PM +0100, GCS wrote: Package: apache2 Severity: wishlist I do not know if it's by any means possible, but as both libdb4.1-dev and libdb4.2-dev provides libdb-dev, would it be possible to depend -dev packages on that? That sounds dangerous; as I understand it, it's necessary for everything that depends on libapr0 to use the same version of Berkeley DB. On a similar note, though, db4.2 is now in unstable, so will the next version of apache2 use it? Uploads of new upstream versions of subversion are waiting for this to happen. (I scanned the debian-apache archives but couldn't find any mention of this.) Thom committed a change to libdb4.2-dev to apache2 HEAD[1] yesterday, IIRC. Absinthe rocks, Daniel [1]: The Debian apache2 SVN repo. -- Daniel Stone[EMAIL PROTECTED] Debian X Strike Force:http://people.debian.org/~branden/xsf/ pgpZGzgkiQb4p.pgp Description: PGP signature
Re: Bug#217134: Setting headers_out is somehow ignored
On Tue, Dec 16, 2003 at 01:14:37PM +0100, Mario Lang wrote:
OK, I have spent some time investigating this problem, and
it seems that the content-type is correctly set, but
not correctly delivered by Apache2:
I've put the following configuration directives into
/etc/apache2/mods-available/xslt.conf (and linked the .conf and .load):
AddType application/xml .xml
AddOutputFilterByType mod-xsltapplication/xml
Then, I placed a file svnindex.xml into /var/www/apache2-default,
which references a .xsl.
When doing w3m -dump_head localhost/svnindex.xml
I get:
HTTP/1.1 200 OK
Date: Tue, 16 Dec 2003 11:57:12 GMT
Server: Apache/2.0.48 (Debian GNU/Linux) DAV/2 SVN/0.33.0 mod-xslt/1.0.0rc1
Last-Modified: Tue, 16 Dec 2003 11:21:37 GMT
ETag: 78958-347-318f7240
Accept-Ranges: bytes
Content-Length: 839
Connection: close
Content-Type: application/xml
application/xml is the same type originally assigned by Apache
before mod-xslt is run.
To verify that mod-xslt does its job right, I inserted
WriteLog calls into src/mod-xslt.c, especailly in
function xslt_set_headers:
if (stylesheet-method){
writeLog(APLOG_DEBUG,method=%s, stylesheet-method);
if (strcmp((char*)stylesheet-method,xml) == 0){
...
And in function xsltparse:
...
xslt_set_headers(f-r-headers_out,f-r-pool,stylesheet);
f-r-content_encoding=apr_table_get(f-r-headers_out, Content-Encoding);
f-r-content_type=apr_table_get(f-r-headers_out, Content-Type);
writeLog(APLOG_DEBUG,content-type = %s,
charset =
%s,apr_table_get(f-r-headers_out,Content-Type),apr_table_get(f-r-headers_out,Content-Encoding));
...
I did pretty much the exact thing with the debs I put up on gluck, with
the same result.
However, this info seems to get lost on the way through apache, since
the final document is reported to have Content-Type: application/xml,
which is basically the Content-Type originally detected for svnindex.xml
Hope this helps anyone more familiar with the new filters
of Apache2. I am sort of stuck here.
You too, hey?
--
Daniel Stone[EMAIL PROTECTED]
Debian X Strike Force:http://people.debian.org/~branden/xsf/
pgp8wGGULVVpt.pgp
Description: PGP signature
