IIS6 and IIRF problems

[Casey Corcoran]

Greetings! I'm hoping someone has some insight with a problem I'm having...

I've installed Taffy 1.0-98 and had things working great using the "index.cfm/my/uri/here" syntax. So the next logical step was getting the URL Rewriting going right? Well unfortunately I've hit a wall :(

I'm running CF 9 on IIS6 with IIRF 2.1 installed. Here's what my ini file looks like, pulled right from the wiki with a slightly different path:

RewriteRule ^/blue-steel/api/(.*)$ /blue-steel/api/index.cfm/$1

Now, when I access the previously working api minus "index.cfm" I have a few different problems:

1. http://mydomain.com/blue-steel/api/
   404 Not Found Error
   
2. http://mydomain.com/blue-steel/api/?dashboard
   Works, I can see the api methods, etc. However the mock client throws the following error (same as if I try to hit directly in browser)
3. http://mydomain.com/blue-steel/api/users/blah
   400 Mime-Type Error

So, my first thought was "Ok the RewriteRule is wrong" and I changed it to this:

RewriteRule ^/blue-steel/api/(.*)$ /blue-steel/foo.cfm?value=/$1

foo.cfm was simply:

<cfoutput>The uri is: #value#</cfoutput>

Which worked fine proving that the RewriteRule WAS doing its job.

As previously mentioned, the api on it's own works fine using "index.cfm" it's just when I try the URL Rewriting that it stops.

Thanks in advance for any help! Sorry I'm a bit of a n00b.

Casey

[Adam Tuttle]

Hi Casey,

After some more thought I remembered something that might be a similar problem: https://groups.google.com/forum/#!topic/taffy-users/1qzWKDa1GKk

Essentially, the advice from that thread would be to change your rule to:

RewriteRule ^/blue-steel/api/(.*)$ /\blue-steel/api/index.cfm/$1

(note the addition of the backslash, which I highlighted in red)... I don't really understand why that worked for the previous poster, but it did seem to do the trick. Maybe it would work for you too?

Adam