You are •specifically telling it• to be treated as an attachment. If you don't want to do that, then stop telling it to!
I really do hope we're missing something here.
It's because the images are being stored in a folder above the public root folder...
Could I just put that as the value of an <img> tag?
If the image isn't accessible directly via HTTP, you can use CF to serve it. Your CF page would have the CFCONTENT tag as you showed in your original post, then you'd use IMG tags in other pages pointing to that CF page:
You wouldn't need the CFHEADER to specify it as an attachment, though - that's only for when you want to prompt the user to download a file without having it handled natively by the browser.
Dave Watts, CTO, Fig Leaf Software
Awesome, that actually worked really well. i didn't know you could do that.
Is there a way to do something similar to documents: so say a pdf or word loads in the browser as opposed to download as well
The same technique works just as well with any type of content, pdf, word, excel, ectra.
But whether it will open in the browser or be a download depends greatly on the user, what browser they are using, what plugins they have in that browser and how they have it configured. But, of course, all of that is out of your control. The most you can do is use the code provided to suggest how the browser should handle the content.
It might also be worth you looking into the CFIMAGE tag with the action="flushtobrowser" attribute, just for completeness.