Hmmm...this is how I've had to do mine from the start (the vhosts, that is). What version were you upgrading from?
Rich -----Original Message----- From: Erik Anderson [mailto:[EMAIL PROTECTED] Sent: Monday, October 31, 2005 12:21 PM To: [email protected] Subject: [gentoo-server] Re: mod_rewrite issue after upgrading to apache-2.0.54-r31 On 10/31/05, Erik Anderson <[EMAIL PROTECTED]> wrote: > I recently upgraded one of my servers to the latest stable apache > ebuild in portage (2.0.54-r31). After upgrading, all of my > mod_rewrite rules stopped working. I have checked the httpd.conf > file, and it appears that the rewrite module *should* be getting > loaded. There are no errors when I start the apache process. > > Has anyone else seen this behavior? Okay - to reply to myself...I made some headway. I determined that if I placed the rewrite rules in the vhost declaration instead of my .htaccess file that they work fine. What's interesting is that I have "AllowOverride All" set for my DocumentRoot, so I would have expected that to enable me to create rewrite rules in my .htaccess. Is this a change in behavior with the new rev of apache? -- [email protected] mailing list -- [email protected] mailing list
