> > What are you trying to do, exactly? If you call the file > > with CFHTTP, what do you want to happen? If you're using > > CFHTTP, you really don't need any of the CFHEADER or > > alternate MIME type stuff; you can just take the results > > of the CFHTTP request and save it as a file from within > > your CF program. > > It's for a custom tag which calls serialised wddx packets, > and deserialises them. Instead of calling the file directly > (such as WAuto.txt), I'd like to call it in such a way that > the developer doesn't know what the filename is, partly for > security (is this pointless?) and partly so if the filename > changes, it won't matter - such as calling it in cfhttp > feed.cfm?f=#this# > > Am I being overly cautious here - does it matter calling the > files directly?
The answer depends on what you want, exactly. If you don't need to secure access to the files, you don't need to write a wrapper to fetch them. If you do need to secure access, then you may want this wrapper. In any case, you don't need to bother with the "downloading" aspects of CFCONTENT - your custom tag can fetch the WDDX packet from the remote server without receiving the HTTP response headers that browsers would need to prompt the user to save the file. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
