Definately remove the cfoutput tags, and the cfheader value should
read attachment; filename=#filename# (you're missing the "filename="
portion)
good luck! :)
> Okay, I added the "filename=" and took off the <cfoutput>,
> and gave my client a list of questions for her customers.
> :) Thanks!
>>> I have searched the archives here, books, and forums at
>>> MM. My client says that the download I gave her works
>>> for
>>> maybe half of her customers. Others are getting .cfm
>>> files, or possibly something else that they can't use.
>>> That is just not acceptable, you know? Here's the
>>> relevant code:
>>
>>> <cfoutput><CFHEADER NAME="Content-Disposition"
>>> VALUE="attachment; #variables.attach#">
>>> <CFCONTENT TYPE="application/x-zip-compressed"
>>> FILE="#form.userfile#" deletefile="no"></cfoutput>
>>
>>> Am I missing an important clue, or is CF just the wrong
>>> thing to use for downloads? My client is selling
>>> downloadable products, so this is crucial.
>>
>>that's pretty much the way I've done it, but then not all
>>browsers
>>adhere to the standards... I'm pretty sure the cfheader is
>>a
>>standardized mechanism. Anyway... try adding ?/#filename#
>>or
>>&/#filename# to the end of the download url, that might
>>trick those
>>browsers which don't comply into seeing the end of the url
>>as the name
>>of the file.
>>
>>s. isaac dealey 954.927.5117
>>
>>new epoch : isn't it time for a change?
>>
>>add features without fixtures with
>>the onTap open source framework
>>http://www.sys-con.com/story/?storyid=44477&DE=1
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
