BlueDragon Server JX "hooks into" IIS via Extension Mappings.
*.cfm is mapped to
By default, the BDJX installer adds these mappings at the Global level of IIS where they are typcially inherited by all
websites. However it is entirely possible to add these mappings (or any other mappings you wish... even mappings that have
nothing to do with BlueDragon) to the level of a specific website instead of Globally.
Our testing here has revealed an interesting quirk about IIS and how it manages Extension mappings (Script maps) defined within it.
Our testing here has shown that once any change is made to the Extension map at the level of a specific website (adding or removing
any mapping) that the inheritance of global mappings becomes broken for that specific website.
In other words, that website will cease to inherit newly added global mappings.
Here is an example you can try yourself to help drive this point home:
Create a brand new website and take note of its extension map.
Specifically take note of the fact that it inherits all the mappings
that exist in the global map.
Add a new extension mapping at the global level, and then view/refresh the
map at the website level again to confirm that it has inherited that newly added
Make a change to the map at the website level by either adding or
removing a mapping.
Repeat #2 above using some new extension value
View/refresh the map at the website level again to see that it has not
inherited that new global mapping.
Once you add or remove any Extension mappings at the level
of a specific website then the Extension map for that site is no longer
inherited from the global map.
Instead that specific site receives its own "copy" of the global
mappings. But from that point forward, the 2 "copies" (the global copy
and the website copy) may very well diverge (broken inheritance).
If you later add a global mapping which does not seem to take effect on requests to that website, then this is why.
In that scenario you must also add that mapping to the website level.