I Changed the rule to check if the index.html file exists to this -

<add input="{DOCUMENT_ROOT}\wp-content\cache\supercache\{HTTP_HOST}\blog\{R:1}\index.html" matchType="IsFile" />

And that works also, it actually loads noticeably faster without hardly a browser post back, though the way it was before I made this change was also pretty instantaneous, I wouldn’t have noticed had it not been doing this one after the other and the last time was super quick. So why would it work both times, if this last time is correct?

The Rewrite Rule is set up in the Web.Config inside of this subfolder and the pattern to match and rule is –

<rule name="WP Super Cache" enabled="true" patternSyntax="ECMAScript" stopProcessing="true">
<match url="(.*)" />

The URL Rewrite rule for the WP Super Catch has this for checking if the file exists -

<add input="{DOCUMENT_ROOT}\wp-content\cache\supercache\{HTTP_HOST}\{R:1}\index.html" matchType="IsFile" />

And the action type is this -

<action type="Rewrite" url="wp-content/cache/supercache/{HTTP_HOST}/blog/{R:1}/index.html" />

When I check the page a second time, it loads quickly from the Super Cache and I check the source and it reads as follows:

<!– Dynamic page generated in 0.990 seconds. –>
<!– Cached page generated by WP-Super-Cache on 2010-04-20 02:51:42 –>
<!– super cache –>

Also my regular WP Rewrite rule for Permalinks is as follows:

<rule name="wordpress" patternSyntax="Wildcard">
<match url="*" />
<conditions>
<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
</conditions>
<action type="Rewrite" url="index.php" />
</rule>

So if you can fill that in with the last post, you’ll see what I mean sorry about that.

Thanks for your reply. I have a detailed explanation of what is happening, but it’s confusing, according to what you’ve explained and what I know of the URL Rewrite Module. I’ll explain below, I think we’re close to having a handle on a confusing issue.

So as stated above, my WordPress blog is set up in a subfolder of my main site like this: http://www.example.com/blog/

The Rewrite Rule is set up in the Web.Config inside of this subfolder and the pattern to match and rule is –

The URL Rewrite rule for the WP Super Catch has this for checking if the file exists -

And the action type is this -

It would seem that the condition to check that the file exists is missing the “blog\” before the {R:1} but when I navigate to a post on my WP blog the post shows correctly with no issues, the folders and index.html file is created by WP Super Cache under the supercache subfolder of cache in the wp-content folder. The folder structure is exactly as it should be, with the blog subfolder in the path.

When I check the page a second time, it loads quickly from the Super Cache and I check the source and it reads as follows:

So this indicates that everything is working fine, the Super Cache is active. But according to the “blog/” not being in the condition that the File Exist, it shouldn’t be. Any idea as to what is going on and if there’s something to fix?

Also my regular WP Rewrite rule for Permalinks is as follows:

This is set up in the Web.config of the blog subfolder and works, but again the lack of having the “blog/” folder mentioned in the rule seems like it wouldn’t allow it to work, if you have any insight into why it does work, please let me know.

I’ll keep on trying different combination and seeing what happens and note anything worthwhile here.

I’ll have to look up doing the Failed Tracing with URL Rewrite, last time I looked into that it was involved. Wouldn’t the RegXp testing feature in the URL Module within the IIS 7 Manager tell me if there’s a match? Or at least tell me what the R:1 is, so I can tell, right?

I think your rewrite rule is correct. I also noticed recently that when WordPress is setup in a subfolder, then this subfolder needs to be included in the rewrite logic. You need to make sure that you include the subfolder in the condition that checks the file existence and then in the action url.

The best way to ensure that your rule is setup correctly is to enable Failed Request Tracing and check if the rule was evaluated successfully.

I have never tried the gzip compression with the wp-super-cache on windows. I do not know if it will work or not.

Thanks for this article it helps running a WP blog on IIS 7 easier. I set up my WP-Supercache like you described in the article.

I wanted to check with you that my Rewrite rule was correct since it appears to be different than what you described in the comment about using sub-folders.

So my site structure is like this:

http://www.mainsite.com/blog/

And WP is in the blog directory. So my rewrite rule is like this:

wp-content/cache/supercache/{HTTP_HOST}/blog/{R:1}/index.html

The mach URL rule uses Regular Expression with this as the pattern: (.*)

I check the pages and it works, the sub folders are created under the supercache folder structure with the index.html pages and I check the Page Source and see the Generated by WP-Supercache on the bottom after refreshing and the timestamp is the same, I’m just wondering since it seems to be different in the Rewrite rule that what you described. In the response to Gail’s comment about subfolders you said to not count the subfolder, so I’m confused a little.

Also the gzip compression is not set up, should I turn this on in the WP-Supercache admin or should I do that on the IIS 7 admin? I’m pretty sure I shouldn’t do both, right?

What is the reason not to use the standard permalink structure?