modrewrite and logging

[iRaS]

i think an improvement for ispcp it would be if the domainuser for each domain can define a logging level for each domain/subdomain/domainalias.

often someone creates rewrite rules and wondering why they don't work. but he can not enable logging cause it's only possible in conf files and not in htaccess files.

shure the admin can define special rules for this account. but this will generate a new ticket for each user that would change the logging level..

i simply added this lines to als_entry.tpl dmn_entry.tpl and sub_entry.tpl after the <IfModule cband.c /> part:

Code:

<IfModule mod_rewrite.c>
        RewriteEngine On
        RewriteLog {WWW_DIR}/{DMN_NAME}{MOUNT_POINT}/rewrite.log
        RewriteLogLevel 3
    </IfModule>

also a button to clear the log file would be suitable. it could simple execute

Code:

echo "" > {WWW_DIR}/{DMN_NAME}{MOUNT_POINT}/rewrite.log

[BeNe]

We use a Pipe for the Logs in the new Version because of too many open Files.
In your case, the open files will grow again...
But no bad idea! Maybe we can improve it ?

Greez BeNe

[iRaS]

shure. it's a just an idea. you can improve it how you want. looking forward to next version

[kilburn]

By the way, RewriteLog gets tons of info, thus slowing down things a LOT. Consequently, allowing users to control it is a really bad idea, as they will enable RewriteLog when something fails but never disable it again after the issue is solved.

IMHO any user playing with the RewriteEngine should locally test their setup before committing to a production server, or they can seriously hurt performance fo the whole server!

[iRaS]

Quote:Maybe we can improve it ?

how a bout a time limit? rewrite log can just be enabled for 10 minutes after 10 minutes the rewrite log will be disabled and on renabling it the log file will be deleted. so both problems (large log files and slowing down server) will be fixed.