Quantcast
Channel: Adobe Community : Popular Discussions - ColdFusion Server Administration
Viewing all articles
Browse latest Browse all 78799

HTM handler mappings not working correctly

$
0
0

We are running Windows Server 2008 with IIS 7 and ColdFusion Server Standard                8,0,1,195765.

There are certain directories where we want to process htm files through ColdFusion, but most htm files should be processes through the ServerSideIncludeModule.

I modified the web.xml file as such:

<servlet-mapping id="coldfusion_mapping_15">
         <servlet-name>CfmServlet</servlet-name>
         <url-pattern>*.htm</url-pattern>
    </servlet-mapping>
    <servlet-mapping id="coldfusion_mapping_16">
         <servlet-name>CfmServlet</servlet-name>
         <url-pattern>*.html</url-pattern>
    </servlet-mapping>
    <servlet-mapping id="coldfusion_mapping_17">
         <servlet-name>CfmServlet</servlet-name>
         <url-pattern>*.htm/*</url-pattern>
     </servlet-mapping>
     <servlet-mapping id="coldfusion_mapping_18">
         <servlet-name>CfmServlet</servlet-name>
         <url-pattern>*.html/*</url-pattern>
     </servlet-mapping>

 

But now, ALL htm files on the site are processed through ColdFusion, even when no directory level mappings have been created for it.  Even when I explicitely create an HTM mapping for a directory and set the extension to process through serverSideIncludeModule, it still processes through ColdFusion.  The directory level settings appear to be ignored.

I navigate to a directory in the IIS Manager, click on Handler Mappings, add a new Module Mapping for HTM as such:

Request Path:  *.htm

Module:  ServerSideIncludeModule

Name:  SSI-Inc

Request Restrictions:  File

Verbs:  Post, GET

 

This appeared to be the correct method for setting this up but it does not work.

Any insight on correct configuration of this feature would be most helpful.

Thanks,

Jim


Viewing all articles
Browse latest Browse all 78799

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>