Ok, im back ;;:-(0) The image is a cfm file (cfcontent) which includes the cfheader tag (works like a charm now), I was confused, for some reason I thought you could only apply the cf header to the html page - I was for some reason thinking that it would create the <meta tag, but it creates the http header... So its all fine now..
-- Taco Fleur Senior Web Systems Engineer http://www.webassociates.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stanton Sent: Wednesday, 22 September 2004 5:27 PM To: CFAussie Mailing List Subject: [cfaussie] RE: No caching of an image Each HTTP request for a file is completely seperate. If you request an image via <img src=... its exactly the same as requesting it directly by typing the URL in your address bar as far as HTTP (and the proxies, browser cache and web servers) is concerned. So setting a CFHEADER for the html page in which the image is to be rendered will have no affect on whether the image gets cached or not. (Well thats not quite true, cookie stuff gets shared across requests, but in terms of caching it pretty well true). Also I don't understand how you are applying CFHEADER to a page that sends the email - the email ends up as a flat HTML file on a mail server which then gets copied into someones inbox - there is no involved HTTP there. Maybe I'm not understanding your properly. -- Mark Stanton Gruden Pty Ltd http://www.gruden.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
