ErrorDocument, preserving environment variables

[samsm]

Apache 2.2

<VirtualHost foo.localhost:80>
  NameVirtualHost foo.localhost
  DocumentRoot /Users/samsm/Sites
 
  RewriteEngine On
  RewriteRule ^/test_forward$ /test.php [QSA,L]
 
  ErrorDocument 404 /test_forward
 
</VirtualHost>

In this example, test.php gets run on a 404, and kindly provided with a REDIRECT_URL server variable, accessible at $_SERVER['REDIRECT_URL']. THis is what you'd expect from http://httpd.apache.org/docs/2.2/cus....html#behavior

Great except I want to take that REDIRECT_URL and use it in the rewrite.
Like:

RewriteEngine On
RewriteRule ^/test_forward$ /%{REDIRECT_URL}/test.php [QSA,L]

But that doesn't work.

Any ideas? Can you use arbitrary environment variables in rewrites? Or am I asking for something that just doesn't work?

Is there another way to intercept 404s and rewrite to another resource?

Thanks!

[samsm]

While a tad messy, %{THE_REQUEST} seems to have what I need.

RewriteCond %{THE_REQUEST} (.*)
RewriteRule ^/test_forward$ /test_forward/original/%1 [C]
RewriteRule ^/test_forward(.*)$ /test.php$1 [P,QSA,L]

[dklynn]

ss,

Oh, my! That makes no sense at all!

First, I've never seen a domain name listed in the VirtualHost opening tag - always the IP Address (that may be because I've lead such a sheltered life ).

Second, you can write your own 404 processing using mod_rewrite's -d and -f metacharacters (existing directory and file checks) and the {REQUEST_URI} (or {THE_REQUEST}) to pass info - I'd put it in a query string, though, and not add it as a directory/file after a filename (MultiViews doesn't like that).

If you need the code, have a look at the tutorial Article linked in my signature - it's in the code section (last half).

Regards,

DK

[samsm]

I got the domain name in the Virtualhost opening tag thing from a common Rails setup. My guess is it resolves that domain once at startup, which probably what most people would do manually. But, now that you mention it, I guess that would break in some circumstances.

Second, you can write your own 404 processing using mod_rewrite's -d and -f metacharacters (existing directory and file checks) and the {REQUEST_URI} (or {THE_REQUEST}) to pass info

This would be a good idea, but in some cases I have to account for application logic determining that there is a 404.

That %{request} data may well end up in a query string, that's just a detail I have worked out yet. Hopefully I'll have a prototype this weekend and I can demonstrate the sense of this.

[dklynn]

ss,

Go for it!

Regards,

DK