Is there a MIME type associated with .js files? You may need to throw a CFCONTENT tag at the beginning of your CFM file to tell the browser that it is definitely a JS file rather than a text or HTML file (which is default for CFM files I believe). The browser shouldn't care about the extension of the filename... only the MIME type offered at the beginning of the file by your Web server. The PC I'm using here doesn't seem to have a mapping for .js, so I can't tell if it uses a separate MIME type or not. Brian At 07:31 AM 04/07/2001 -0400, you wrote: >Date: Fri, 06 Apr 2001 23:27:55 -0400 >From: "Steve Reich" <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: CF Server parsing .js files... >Message-ID: <[EMAIL PROTECTED]> > > > That's the way we do it... works like a champ. When your stylesheets get > > big, you really should link to them, rather than include them, so that > > browsers can cache them and speed up all your pages. Works for us in > > Netscape, too, vs. Steve's experience in the next post. > > >It's not a stylesheet. It's a javascript source file that I'm trying to >include with CF variables.... > >This works fine in IE and NS... > > <script language="javascript" src="myfile.js"></script> > >This works in IE but not in NS... > > <script language="javascript" src="myfile.cfm"></script> > >I'm thinking I need to find another approach to what I'm trying to do. >Netscape seems to need the .js extension to reference as a valid source >file. > >Steve Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
