| 1 |
Hmmm...this is how I've had to do mine from the start (the vhosts, that |
| 2 |
is). What version were you upgrading from? |
| 3 |
|
| 4 |
Rich |
| 5 |
|
| 6 |
|
| 7 |
-----Original Message----- |
| 8 |
From: Erik Anderson [mailto:erikerik@×××××.com] |
| 9 |
Sent: Monday, October 31, 2005 12:21 PM |
| 10 |
To: gentoo-server@l.g.o |
| 11 |
Subject: [gentoo-server] Re: mod_rewrite issue after upgrading to |
| 12 |
apache-2.0.54-r31 |
| 13 |
|
| 14 |
|
| 15 |
On 10/31/05, Erik Anderson <erikerik@×××××.com> wrote: |
| 16 |
> I recently upgraded one of my servers to the latest stable apache |
| 17 |
> ebuild in portage (2.0.54-r31). After upgrading, all of my |
| 18 |
> mod_rewrite rules stopped working. I have checked the httpd.conf |
| 19 |
> file, and it appears that the rewrite module *should* be getting |
| 20 |
> loaded. There are no errors when I start the apache process. |
| 21 |
> |
| 22 |
> Has anyone else seen this behavior? |
| 23 |
|
| 24 |
Okay - to reply to myself...I made some headway. I determined that if |
| 25 |
I placed the rewrite rules in the vhost declaration instead of my |
| 26 |
.htaccess file that they work fine. What's interesting is that I have |
| 27 |
"AllowOverride All" set for my DocumentRoot, so I would have expected |
| 28 |
that to enable me to create rewrite rules in my .htaccess. Is this a |
| 29 |
change in behavior with the new rev of apache? |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-server@g.o mailing list |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-server@g.o mailing list |
Archives