Wrong Status Codes in IIS LogFile when using IIRF

Topics: Developer Forum
Feb 3, 2012 at 10:11 AM
Edited Feb 3, 2012 at 10:12 AM

Hi together,

In my application the user gets redirected to a specific page when entering the www addresse:

www.mydomain.com -> www.mydomain.com/start  |  status code normaly 301

By looking to my firebug network console everything looks fine and it shows the corect status code (sc) - 301 moved permanently. But if look at the log file from my IIS6 it loggs sc 200 - WHY????

I deleted the IRFF from the ISAPI filters and everything logged in the right way. It does not depend on my application. It has to depend on the IIRF.

A simalar problem occured if the logfile should write a 404 status code:

www.mydomain.com/test.htm | firebug: 404 | IIS log: 200

www.mydomain.com/test | firebug: 404 | IIS log: 404

I think thats strange and I don't really know a solution for that.

Thank you for your help

Greets Dirk

By the way my ini file:

------------------------------------------------------------

# Iirf.ini
#
# ini file for IIRF
#

RewriteLog C:\logs\iirf
RewriteLogLevel 5
RewriteEngine ON
StatusInquiry ON

RewriteRule ^/download.cfm(.*)$ - [L,I]
RewriteRule ^/404.html$ - [L,I]
RewriteRule ^/cms/(.*)$ - [L,I]

RewriteCond %{APPL_PHYSICAL_PATH}$1 !-f
RewriteCond %{APPL_PHYSICAL_PATH}$1 !-d
RewriteRule ^/([^.]+)\?(.*)$  /index.cfm?content=$1&$2 [L]
RewriteRule ^/([^.]+)$  /index.cfm?content=$1 [L]

Coordinator
Feb 4, 2012 at 12:03 AM

Hmm, I don't know about that.

I think you'd need to provide some additional information on the situation, in order to be able to diagnose it.

Rather than look into the 301, which involves 2 distinct request+response HTTP transactions, in the interest of simplifying, I'd suggest that you focus on the 404 NF return code.

I don't see anything in the IIRF that generates a 404, so I don't see how that situation could have gotten triggered.

Maybe you could just focus on that, and see if you can diagnose that.