Ian,

    Excellent explanation. You could not have been more clear. However, 
can you provide me with instructions in how to accomplish this? So CF 
will process the request and spit HTML with a html extension?

Thanks, Ravi.


Ian Skinner wrote:
> Ravi Gehlot wrote:
>   
>> Hello,
>>
>>     I didn't follow this thread closely. But I am curious as to what you 
>> guys were discussing. How would I customize my webserver settings so 
>> that .js files are parsed by CF and why would I want to do that? I know 
>> that JS files are only text files and as far as I know there aren't any 
>> special settings to parse it.
>>     
>
> It is possible to configure the web server and the ColdFusion 
> application server to pass *any* file to ColdFusion for processing other 
> then the default normal, cfm, cfc, cfr, etc file extensions.  This is 
> sometimes done so that ColdFusion processes normal htm|html files, 
> usually for server obscurification, i.e. to hide that the server is 
> making use of ColdFusion.  It can also be done to preserve established 
> links to an older html site that is converted to cfml. 
>
> It would be rather unusual to do this for JavaScript files, but it is 
> technically possible.  The benefit is that you could have linked 
> JavaScript files dynamically built with CFML.  The downside is that it 
> interferes with normal browser caching of linked script and|or style 
> files, the same thing can be done with CSS files.  Sometimes it is worth 
> the trade off and|or there are ways to mitigate the downside with 
> <cfheaders...> etc. 
>   


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to 
date
Get the Free Trial
http://ad.doubleclick.net/clk;207172674;29440083;f

Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:316985
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to