From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] [Apache HTTPD] Why doesn't my RewriteRule fire?
Date: Mon, 22 Aug 2011 14:07:50 -0700 [thread overview]
Message-ID: <CAE1pOi3oHj5yO88=KtA1KUstne9w8GxDfEgTKz55Aks1BtZr4w@mail.gmail.com> (raw)
Hi all,
I hope some Apache guru can help me out. I must be missing something
very obvious.
Assume a default Apache 2.2.17 with all modules installed and -D PROXY
-D INFO in /etc/conf.d/apache2.
My update to the default VHOST:
ForensicLog /var/log/apache2/forensic.log
ProxyRequests off
RewriteEngine on
RewriteLogLevel 9
RewriteLog /var/log/apache2/rewrite.log
<VirtualHost *:80>
ServerName localhost
ServerAdmin root@localhost
DocumentRoot "/var/www/localhost/htdocs"
<Directory "/var/www/localhost/htdocs">
Options Indexes FollowSymLinks
AllowOverride All
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Directory>
RewriteRule ^/website$ http://localhost/website/ [T]
ProxyPassMatch ^/website/(.*)$
http://localhost:8000/website/$1
</VirtualHost>
The ProxyPassMatch fires but (AFAICT) the RewriteRule does not. I.e.
http://localhost/website (no slash) ==> 404 (in fact, it's trying to
serve /var/www/localhost/htdocs/website) but http://localhost/website
(with slash) ==> works.
Why does the RewriteRule not run? FYI, rewrite.log is created but
stays empty. I don't see any errors or warnings in access.log or
error.log.
Cheers,
Hilco
next reply other threads:[~2011-08-22 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 21:07 Hilco Wijbenga [this message]
2011-08-22 21:31 ` [gentoo-user] [Apache HTTPD] Why doesn't my RewriteRule fire? Paul Hartman
2011-08-22 22:13 ` Hilco Wijbenga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE1pOi3oHj5yO88=KtA1KUstne9w8GxDfEgTKz55Aks1BtZr4w@mail.gmail.com' \
--to=hilco.wijbenga@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox