>Number: 2556 >Category: general >Synopsis: RewriteRule generates redirect (code 301) but code 200 is >logged >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Jul 6 10:10:01 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.0 >Environment: Red Hat Linux 4.0 + updates, Linux kernel 2.0.34 >Description: I have the following 3 rewrites:
RewriteRule ^/~cadams/(.*) /bleh/$1 [R=301,L] RewriteRule ^/bleh$ /bleh/ [R=301,L] RewriteRule ^/bleh/(.*) /~cadams/$1 [PT] This makes http://ro.com/bleh go to the page for user cadams and run everything as that user (through suexec), and attempts to go to http://ro.com/~cadams are redirected to http://ro.com/bleh for log purposes (so there is only one way to get to the page). Everything works okay except for one thing: when I go to http://ro.com/bleh/, I get a redirect to http://ro.com/bleh/index.html. This is okay, except that it is not logged as a redirect: 205.216.92.19 ro.com - [06/Jul/1998:11:54:16 -0500] "GET /bleh/ HTTP/1.0" 200 233 "-" "-" This makes log analysis programs think that this is a normal hit, when it is not. >How-To-Repeat: You can go to the above URLs to see the results. >Fix: Is there a better way to make http://ro.com/bleh map to http://ro.com/~cadams but still get everything run through suexec? >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
