thanks for your reply. I am sorry that I was not able to express myself clearly enough, the reason is that I am new to IIS direct administration and usually I only configure it using Parallels Plesk. I am more used to Apache, which uses the term "vhost"
for any virtual hosts, i.e. multiple domains served by one physical server with a single IP address.
There are so many different terms for IIS: "virtual directory", "application", and there are "vhost" directories in "C:\Inetpub\" like "C:\Inetpub\vhosts\default\htdocs", "C:\Inetpub\vhosts\domain1.tld\httpdocs", , "C:\Inetpub\vhosts\domain2.tld\httpdocs",
..., which I guess are just the physcial directories for the vdirs...?
Now back to explain what I did.
I installed it "server-wide". That's what I selected in the installation wizard (and also when I installed it manually, I used the "websites" category (or tree item) of the IIS Administration tool, not the category name / subtree item of an individual web
site (or web application?)).
Now, if you say "If you are merely using multiple vdirs, and if your IIRF is installed at the server level, then it should "just work".", then I guess that's what I do (without knowing it for sure). As I said, I have multiple physical directories like
For each of the "C:\Inetpub\vhosts\domain?.tld\httpdocs" directories, there is a subtree item under the "websites" tree item in the IIS Administrator application.
Therefore I guess, I am just using multiple vdirs. (Is that so, how can I tell?)
But on the other hand, I now de-installed everything, then manually installed it for just one web site (application / vdir / whatever).
In that case, I can call /iirfStatus and watch the results page (I replaced the actual domain name by domain?.tld):
IIRF Status Report
IIRF Global Status
IIRF Version Ionic ISAPI Rewriting Filter (IIRF) 18.104.22.168 x86 RELEASE
Built on Aug 17 2011 09:58:52
Filter DLL C:\WINDOWS\system32\inetsrv\iirf\IIRF.dll
PCRE Version 8.02 2010-03-19
IIRF Started 2011/08/25 15:06:15 Mitteleuropäische Sommerzeit
Current time 2011/08/25 15:43:12 Mitteleuropäische Sommerzeit
Server Ini file C:\WINDOWS\system32\inetsrv\iirf\IirfGlobal.ini
Last Update of Ini 2011/08/21 22:56:22 Mitteleuropäische Sommerzeit
Rewrite Engine (all vdirs) ON
IIRF Vdir Status
Root Vdir Ini File C:\Inetpub\vhosts\domain.tld\httpdocs\Iirf.ini
Ini file timestamp 2011/08/23 19:49:46 Mitteleuropäische Sommerzeit
Last read 2011/08/25 15:06:15 Mitteleuropäische Sommerzeit
#Ini Modules 1
Log file C:\temp\rewrite\rewrite.20304.log
Log level 3
Rewrite Engine ON
Rewrite Base '--'
Remote Status Inquiry enabled
Cond substring flag *
Case conversion flag #
URL Decoding ON
Iteration Limit 8
Proxy Timeouts (sec.) Resolve=30 Connect=30 Send=30 Receive=30
#Requests Processed 10
What makes me think that I am NOT just using just vdirs is that I had to grant extra rights to the log file directory to the specific webuser (can't remember exactly, but I think it was something like "IUSR_xyz", where xyz was the domain user.
And, after log files were successfully created, they had a different process ID.
Also, the APPL_MD_PATH is different from that of the default website: /LM/W3SVC/16099/Root vs. /LM/W3SVC/1/ROOT.
I read in the documentation, that IIRF needs to load the DLL for each w3scv.exe process individually, and hence cannot redirect/rewrite across multiple domains running on the same physical server. As I understand it, IIS creates a w3svc for each domain (web
application) for security reasons.
Could it be that under these circumstances, I cannot use a server-wide installation, without forcing IIS to run in IIS 5.0 compatible mode (which I am not allowed to do)?
Anyways, even though I am too dumb to get it up and running server-wide, it seems to be great work. The documentation is really good and as far as I can see, it is pretty much compatible to Apaches mod_rewrite. Only thing that really annoys me is that I
seem to be the only one not being capable of getting it running server wide.