Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I'm finally getting around to configuring the SuSE 9.3 web server on the new box. The split apart config files is probably a better design, but it's causing me some confusion. I'm working on the virtual hosts (I have about 8 or so). I finally figured out that listen.conf needed to be modified for virtual hosts. That was documented if you actually looked at that file. But it totally baffles me why you need to set up a Virtual Host for the default web server, when the DocumentRoot and logfiles etc are already defined in that case. And if you need to do that, why doesn't the template default-server.conf have a VirtualHost section in it, guaranteeing that one would be first? So I got all that happening, and set up my second VirtualHost. It cam up with the right DocumentRoot, however I got a file listing instead of index.html! After putting a DirectoryIndex entry in that VirtualHost block, it worked as expected. But if the sever's default configuration (not default-server.conf, but httpd.cong) has a DirectoryIndex entry, how come the VirtualHost didn't use that setting for the default? How are you supposed to handle that? I find it hard to believe that the same 20 or 30 options like that need to be hard-coded in each VirtualHost config file. What other settings from httpd.conf won't carry over into a vhost.d/*.conf file? -- ---------------------------------------------------------------------------- DDDD David Kramer david at thekramers.net http://thekramers.net DK KD DKK D Isn't the universe an amazing place? DK KD I wouldn't live anywhere else. DDDD J'Kar
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |