Re: rewrite.php or redirect.php

am 06.01.2001 18:58 Uhr schrieb Lewis Bergman unter lbergman@abi.tconline.net: >> Three problems/questions: >> 1) The variables passed to the "does_not_exist.php" to not >> automatically turn into PHP-variables. Nor "include " neither "require" >> allow passing variables via a HTTP-query string. So a (time consuming?) >> walk through some arrays needs to be done? > I am not sure what you mean about the file. The arg passed to the 404.php > file would be the one redirected FROM like this: > 1. in the server config part of apache > ErrorDocument 404 /404.php > 2. someone types "www.yourserver/ttttttt.php and it isn't found > 3. The variable passed to 404.php in all the REQUEST_URI tupe vars will be > ttttttt.php. Is this what you are asking? No, I mean those passed via GET or POST. > >> 3) Since this behaviour can be the standard one (instead of finding the >> requested doc by first hit) the error_log will definitely explode. >> (Okay, can be cleaned by cron, but makes it hard to find the 'real' >> mistakes) > Are you thinking of redirecting _everything_ to 404? That seems odd. I > cannot imagine (if this is really what you mean) why you would do that. Because I want to make "standard" PHP files, which reside in some "..../default/" directory. But I want to be able to replace or overwrite these standard files - whereever necessary - with customized ones: be the reason language (".../default/en" or ".../default/de"), or customization demands from customer (".../company1/" or ".../company2/"). If there is one customized take this. If there is no customized version use the standard. You know, like in C++ classes that inherit things from their parent class but can be overwritten. I know how to do both ways codewise, I´m still not shure which way would be more performant? Regards Tino www.interpool-online.de