>I ran thru that procedure exactly and got the same CF 'file not found'
>error. Just to make sure I pulled the path from an Explorer window
>and it blew up as well, so it wasn't a spelling error.
Instead of using CFHTTP or CFINCLUDE, have you tried doing a server-side
forward?
<cfscript>
getPageContext().forward("relativeURL");
</cfscript>
This would be similar to a <cflocation />, but it happens purely on the
server (no 302 header is sent to the client.)
This would have less overhead than the CFHTTP call and you shouldn't see the
problems you're seeing w/CFINCLUDE.
-Dan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227467
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
