Random behaviour

[billybunter Profile]

Hi
I have been working with our installed licenced application. V 3.1.0.87

I have found some very random behaviour which has caused me hours of frustration.

e.g.
Creating a rewriterule, then deleting it, and it still working for at least 5 hours
Creating a rewriterule, it not working for many hours, then working, possibly after an IIS reset
I was using
RewriteRule ^([^.?]+[^.?/])$ $1/ [R,L]
RewriteRule ^mississippi-cruise$ /cruises/mississippi-river-cruising/all [NC,R=301,L]
To re-direct a folder request to a different one.

Switching on the logging in httpd.conf, then switching it off and the logging staying on despite an IIS reset
# Logging
# RewriteLog specifies log file.
# RewriteLogLevel specifies verbosity. 0 = none, 9 = all.
# RewriteLogLevel 9
# LogLevel is for general logging for config file loading problems, not rewriting. Default is warn.
# LogLevel debug

This is driving me nuts. This is a live server and you say that I shouldn't be running error logging, but I can't switch it off!

Do you have any ideas for resolution?
Thanks

[Anton]

Hello,

"Creating a rewriterule, then deleting it, and it still working for at least 5 hours
Creating a rewriterule, it not working for many hours, then working, possibly after an IIS reset"
- these situations are classical in case of insufficient permissions.
Please make sure List folder content permissions are granted.

"Switching on the logging in httpd.conf, then switching it off and the logging staying on despite an IIS reset"
- this one is more weird, but the primary concern is definitely permissions - for some reason changes to the config are not applied.

- Does ISAPI_Rewrite generally work? Could you please show the error.log records it generates (you can send them to [email protected] with reference to this forum post).

- also please consider updating to the latest build (104) which has definitely fixed some minor bugs.

[billybunter Profile]

Thank you very much for your help Anton. Soooo fast and helpful.

Permissions
One of the things about the permissions that I don't get is that I can add a rule to .htaccess and it can work immediately
But then another rule can hang around for hours after deletion

I have reviewed the permissions and the status of httpd.conf currently
[The Everyone user is able to write to this file]
I have reviewed the permissions of error.log and it have read, write and execute for the Everyone user.

I have made reference to this page - http://www.helicontech.com/isapi_rewrit ... curity.htm but the document is not very specific to my situation, IIS7 and Win Server 2008 so of limited help.

System account has modify for this folder - "C:\Program Files\Helicon\ISAPI_Rewrite3"

On my system, the AppPool is unique. Do you have a permissions document that is more specific to IIS7?


Updating to the latest build
That is a good idea, but bearing in mind it is a production server, will there be issues/downtime?
Thanks again for your brilliant support.
Regards

[Anton]

Hello,

"Soooo fast and helpful."
- hope you are not sarcastic as I haven't helped you much so far

"One of the things about the permissions that I don't get is that I can add a rule to .htaccess and it can work immediately. But then another rule can hang around for hours after deletion"
- sorry, but there is generally no other reason for that except inability of ISAPI_Rewrite to monitor file changes which is due to absent List folder content priviledge or other NTFS permissions. It would be helpful if you could give Everyone Full permissions (for ISAPI_Rewrite install folder and site root with .htaccess) for just 5 minutes to see if it makes the difference and then revert it.

"System account has modify for this folder"
- Please make sure this is the account assigned to the app pool.

"but bearing in mind it is a production server, will there be issues/downtime?"
- updates are usually seamless, but of course it is advisable to test on dev machine first.