Tag Archives: apache

Apache training, day 5

Day 5 of the Apache training has normally been pretty rushed, and an opportunity to cover last minute stuff before people dashed off to the airport. Well, I’ve decided to add real content to day 5, so that 1) people really feel that they are missing something if they leave early, and 2) so that the notes that they have to take with them are actually worthwhile for that last day.

So, I’ve added quite a bit about mod_dav, mod_rewrite, and mod_proxy, as well as a complete treatment of migrating to Apache 2.0.

I suppose I really aught to write some “slides” for this content, but I tend to consider that somewhat less important, so I’ll just probably have all the examples up on the screen while I talk about stuff.

Listen, Port, Bindaddress

Yesterday started training again. I find myself wondering, yet again, why the default configuration file uses ‘Port 80’ rather than ‘Listen 80’, while the documentation says that Port and Bindaddress are deprecated. I’ll have to experiment with setting Listen, and not setting Port, and see if any bad things happen. The only strange thing that comes to mind is that Port has a default value of 80, so if we leave it out entirely, it is still set to 80. I think.

These classes invariably bring up something in the docs that could be done better. Which is pretty cool. It’s like these folks are contributing to Apache just by virtue of letting me talk at them. šŸ˜‰

Magic userdir urls with Perl

I am still experimenting with this Movable Type thing. This is an
attempt to determine two things. First, if I can do this with w3m, which
does not support javascript – there seems to be a lot of javascript
scattered about. Second, if I can do any decent html markup, or whether
this will be painful. Anyways, this article is the same as something
that I just posted on Advogato, and I just want to see if it will look
right.

Note: This sort of worked via w3m, but I still had to go back to a javascript-enabled browser to get the page to actually show up here. Oh well.