httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Rudolph <r...@apple.com>
Subject [users@httpd] Reasons why mod_rewrite won't be executed on an incoming request
Date Fri, 08 Feb 2008 17:08:37 GMT
Hello,

I'm running 2.2.6 of Apache (the standard installation on Mac OS X  
10.5 (Leopard) Server). I'm trying to get mod_rewrite to work with a  
couple of simple rules (one is contrived the other is what I'm really  
after - trying to figure out why it doesn't work).

- rewrtite_module is installed
- these following lines are added to my httpd.conf file:

	RewriteEngine On
	RewriteLog	"/rewrite.log"
	RewriteLogLevel	10

	RewriteRule	^/elk\.html$  moose.html [L]				# contrived example
	RewriteRule	^feedapi cgi-bin/feedapi.cgi [PT]			# make all requests  
for /feedapi passthrough to cgi-bin/feedapi.cgi

If I restart the webserver and attempt to access http://<server- 
address>/elk.html I get a 404 error. Same thing goes for a request  
http://<server-address>/feedapi?...
  If I look at the rewrite.log it is empty save for the following  
which we triggered by the server restart.

127.0.0.1 - - [06/Feb/2008:11:37:13 --0800] [127.0.0.1/sid#10080b670] 
[rid#100a6fe98/initial] (2) init rewrite engine with requested uri / 
server-status
127.0.0.1 - - [06/Feb/2008:11:37:13 --0800] [127.0.0.1/sid#10080b670] 
[rid#100a6fe98/initial] (3) applying pattern '^/deer\.html$' to uri '/ 
server-status'
127.0.0.1 - - [06/Feb/2008:11:37:13 --0800] [127.0.0.1/sid#10080b670] 
[rid#100a6fe98/initial] (3) applying pattern '^/feedapi' to uri '/ 
server-status'
127.0.0.1 - - [06/Feb/2008:11:37:13 --0800] [127.0.0.1/sid#10080b670] 
[rid#100a6fe98/initial] (3) applying pattern '.*' to uri '/server- 
status'
127.0.0.1 - - [06/Feb/2008:11:37:13 --0800] [127.0.0.1/sid#10080b670] 
[rid#100a6fe98/initial] (4) RewriteCond: input='GET' pattern='^TRACE'  
=> not-matched
127.0.0.1 - - [06/Feb/2008:11:37:13 --0800] [127.0.0.1/sid#10080b670] 
[rid#100a6fe98/initial] (1) pass through /server-status

So something is triggering the rewrite engine for the /server-status  
request, but never for any other incoming request. Is there something  
glaringly obvious that I'm missing here?

Thanks,
Rudy.

--
Chris (Rudy) Rudolph
rudy@apple.com

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message