can't enable rewrite log
2 posts
• Page 1 of 1
can't enable rewrite log
Hi All,
We have trouble to enable detail log in Helicon APE.
In the Httpd.conf, we have already added,
Loglevel debug
ErrorLog error.log
RewriteLog rewrite.log
And in the .htaccess, we added
RewriteLogLevel 9
But rewrite.log is still empty.
Can you help us to enable the detail log?
PS: we have both Helicon Rewrite and APE running together. Can you do that or we need to migrate Rewrite to APE?
Thank you!
We have trouble to enable detail log in Helicon APE.
In the Httpd.conf, we have already added,
Loglevel debug
ErrorLog error.log
RewriteLog rewrite.log
And in the .htaccess, we added
RewriteLogLevel 9
But rewrite.log is still empty.
Can you help us to enable the detail log?
PS: we have both Helicon Rewrite and APE running together. Can you do that or we need to migrate Rewrite to APE?
Thank you!
Re: can't enable rewrite log
Hello.
1. Log is probably not written because of insufficient NTFS permissions. With new builds of Ape log rotation has been introduced. Please use only log level directives without specifying exact log location, in this case logs will be written into /logs/ folder under Ape installation, which already has required permissions for IIS_IUSRS:
2. Having both ISAPI_Rewrite and Ape is possible, although redundant. Ape already includes mod_rewrite module that surpasses ISAPI_Rewrite by features and uses similar syntax. Both products will load .htaccess files as their configurations, which sometimes may lead to issues as rewrite rules may be applied twice. However Ape in conformance to Apache does require "RewriteEngine On" directive in .htaccess file to activate rewriting engine and in ISAPI_Rewrite rewriting engine is always on, so if you decide to keep ISAPI_Rewrite installed, just make sure you removed "RewriteEngine On" from .htaccess so Ape will not try to process rewrite rules.
1. Log is probably not written because of insufficient NTFS permissions. With new builds of Ape log rotation has been introduced. Please use only log level directives without specifying exact log location, in this case logs will be written into /logs/ folder under Ape installation, which already has required permissions for IIS_IUSRS:
- Code: Select all
Loglevel debug
RewriteLogLevel 9
2. Having both ISAPI_Rewrite and Ape is possible, although redundant. Ape already includes mod_rewrite module that surpasses ISAPI_Rewrite by features and uses similar syntax. Both products will load .htaccess files as their configurations, which sometimes may lead to issues as rewrite rules may be applied twice. However Ape in conformance to Apache does require "RewriteEngine On" directive in .htaccess file to activate rewriting engine and in ISAPI_Rewrite rewriting engine is always on, so if you decide to keep ISAPI_Rewrite installed, just make sure you removed "RewriteEngine On" from .htaccess so Ape will not try to process rewrite rules.
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 3 guests