I am wondering ways to get the "real" asked for URL, when utilizing mod_Rewrite. You will find several rewrite rules during my htaccess-apply for caching-reasons: First there's a cheque, if your cache-file is existent. If that's the case, the request is going to be rewritten towards the cache-file. Otherwise the request is going to be rewritten to some php-script, which produces this cache-file.

However I suspect, the guidelines does not match like I would like these to. It is possible to possible ways to trace the "real" demands to determine, which URL was asked for through the client and which file is asked for without anyone's knowledge?

Thanks ahead of time.

You might want the %{THE_REQUEST} special variable. The mod_rewrite docs say this:

The entire HTTP request line sent through the browser towards the server (e.g., "GET /index.html HTTP/1.1"). This doesn't include any extra headers sent through the browser. This value is not unescaped (decoded), unlike other variables below.

Therefore if someone makes its way into http://your-domain/path/file.html to their browser as well as your webserver rewrites /path/file.html into something entirely different, the % variable it's still GET /path/file.html HTTP/1.1, or something like that similar.

For exactly what the request finally got rewritten to, you are able to switch on logging for rewrite to determine what it's:

    RewriteLog /some-path/rewrite.log
    RewriteLogLevel 9

This could use your virtual host config and just be utilized for debugging reasons. The rewrite.log file will contain particulars around the spinning process and exactly what the final URI is.