[11:03] <FoxHound01> is there someone who knows how to setup access control and authentication on the cgi-bin directory in apache2?
[11:13] <Kolan> the same way as setting up a access control for every webfolder in apache..
[11:15] <Kolan> Fox: this might help you out: https://wiki.ubuntu.com/ApacheMySQLPHP#head-c353cd3c0a06dae032ab869150ffab7911ede57e
[11:38] <FoxHound01> where would ubuntu keep an Apache2 config file for SSL servers?
[11:39] <FoxHound01> because my htaccess works on http but not on https
[11:45] <infinity> Are you sure you're using apache2 for SSL, and not, say, a completely different webserver (like apache-ssl)?
[11:45] <infinity> That seems to be a common mistake.
[11:45] <infinity> If you never set up apache2 for SSL, you're probably not using it, since it's not configured for SSL out of the box (currently)
[11:57] <FoxHound01> i set it up for apache2
[11:59] <FoxHound01> wait
[11:59] <FoxHound01> i think so
[11:59] <FoxHound01> how would i set it up for apache2?
[11:59] <FoxHound01> because i only have apache2 installed, and can connect to my server using SSL
[12:00] <FoxHound01> hmm
[12:00] <FoxHound01> i have...
[12:00] <FoxHound01> wow
[12:01] <FoxHound01> im confuzed
[12:01] <FoxHound01> apache2-common, apache-common, apache-perl, apache-ssl
[12:01] <FoxHound01> packages installed
[12:01] <FoxHound01> but NOT "apache"
[12:01] <FoxHound01> so am i running apache 2 or apache 1.3?
[12:03] <infinity> Both.
[12:04] <infinity> Or, wait.
[12:04] <infinity> You don't have any "apache2-mpm-*" package installed at all?
[12:05] <infinity> Then you have two versoins of apache1.3 installed (apache-perl and apache-ssl)
[12:05] <infinity> And no apache2 at all.
[12:47] <FoxHound01> i got it all figured out
[12:48] <FoxHound01> apache1.3 was doing the ssl, while apache2 was doing the port 80 http
[12:48] <FoxHound01> lol, night
[12:53] <spike> I thought apache1.3 wasnt even available on dapper...
[12:53] <spike> maybe he was running breezy
[12:54] <infinity> It's still in universe.
[12:54] <spike> ah, I see
[12:54] <infinity> It'll take a long time to kill every apache1.3 installation in the world.
[12:57] <spike> speaking of, I while ago I sent an email, with patch attached, about some comments on apache2 defaults...
[12:57] <spike> never got a reply :/
[12:57] <spike> at least some comment like "you sux" would been appreciated :)
[12:58] <Toadstool> hi here
[12:58] <infinity> spike: Sent it to whom?
[12:58] <spike> because that's what I'm doing, so if the ideas are wrong I'd benefited from confrontation anyway
[12:58] <spike> infinity: to the server ml
[12:58] <infinity> Must have been before I got around to subscribing.
[12:58] <spike> benefit*
[12:59] <infinity> Erm, you seem confused.
[01:00] <spike> ok :)
[01:00] <infinity> mod_vhost has nothing to do with being able to see /doc/ ...
[01:00] <Toadstool> i'm trying to improve my wide-dhcpv6 package... what do you think the default configuration for the client should be? stateful conf or stateless one (only dns info for example), assuming the address is obtained using stateless autoconf?
[01:01] <infinity> In fact, mod_vhost really has nothing to do with anything except mass virtual hosting.
[01:02] <infinity> spike: Your first two points (about the misplacement of configuration for "/" and "NameVirtualHost") are well taken, though, and I'll probably move those around a bit for the 2.2.x package, but won't touch the established settings in the 2.0.x series.
[01:02] <infinity> spike: But, mod_vhost_alias has NOTHING to do with NameVirtualHost. :)
[01:03] <infinity> spike: Simple Name and IP virtual hosting works without any modules loaded.
[01:04] <spike> ah, doh!
[01:06] <infinity> Well, I'll admit that after adminstering apache sites for over a decade, and hacking directly on apache for about half that, I don't tend to really know where it may be "hard" or "confusing", because I know it inside out and backwards.
[01:07] <infinity> So suggestions (filed as wishlist bugs in either Debian or Ubuntu) on how to make things make more sense to first time users will be considered (though not always implemented, I'll admit)
[01:10] <Toadstool> no opinion about my question? too bad, i'll toss a coin ;)
[01:12] <spike> infinity: maybe I misunderstood you, but would you say that's the case for "/" and "NameVirtualHost" comments too? exepecially "/" imho looks more like a config design error than "things made easier for first time user". So I'd rather file / and NameVirtualhost as bugs, and /doc and default vhost as wishlist for "first time user". what do you think about that?
[01:12] <infinity> Toadstool: Not really, no.
[01:13] <spike> 's*
[01:13] <infinity> spike: The default vhost's DocumentRoot is set the way it is on purpose (including not having the RedirectMatch enabled by default, because it confused a lot of first time users), so please don't file that one again. :)
[01:14] <Toadstool> well i'll try to find an IPv6 guru ^^
[01:14] <Toadstool> thanks anyhow
[01:14] <infinity> spike: /doc/ works here, so I'd like to see why it's not workign for you.
[01:14] <infinity> spike: The misplacement of "/" and "NameVirtualHost" are on my TODO, and will be fixed in the 2.2.x SVN repo, so no point in filing them (no, I won't fix them the 2.0.x, because I don't feel the urge to upend people's expectations of hor the config works on a minor version bump)
[01:15] <infinity> ie: If people upgrade from 2.0.54 in breezy to 2.0.56 in dapper, I'd prefer not to surprise them too much with config changes.
[01:15] <spike> infinity: fine for me, tnx.
[01:15] <infinity> But when they go to 2.2.x in dapper+1, they should be expecting some major changes anyway, so that's the time to fix the more annoying oopses.