Note: This blog post is from 2014. Some content, links and indeed comments from others may be outdated--though not necessarily. Corrections are welcome, in the comments. I may revise the content if necessary.There was an interesting solution proposed today on the Adobe forums, to address a problem some folks are having with CF10, where they find problems using an IIS 404 error handlers set to pass to a CF page. I found it helped with one of my consulting clients, so I wanted to share the news with others readers here who may benefit.
The problem is that some folks are finding that their CFML-based IIS 404 handlers either don't work at all or work only sometimes, other times getting connection reset errors. It's plagued folks for months, and while Adobe has suggested a pending new connector may help, it's caused a lot of heartburn, as discussed in this particular forum thread.
About the proposed new fix
So some good news is that today someone offered an interesting different solution that worked for one of my clients. (The person identified themselves only as chickity china, which some may recognize as a BNL song but I know from a funny radio phone prank audio clip from the 90's, and which I just found on youtube.)
Anyway, he (or she) offers some XML to modify the iis configuration, to implement an alternative processing of 404's using an IIS rewrite rule instead. Unfortunately, he doesn't offer much explanation of his approach.
So I followed up with a comment explaining things in more detail, especially if you can't edit the XML or prefer to use the IIS interface features, or want to do it at the server level.
The actual fix
See first the poster's original comment (it's #36 in the very long thread going back almost 18 months, so you may not want to read them all.)
But before applying what he says, do see my follow-on comment for more.
And indeed I then followed with a couple other follow-up comments, one confirming that it did work for a client suffering the problem, and another pointing out something else to be wary of when having IIS pass *all failed file requests* to CF. See my comments there for more.
Hope all this may help some folks.
For more like this: