ACS serving files with Content-Disposition header

Hi,

I almost started this discussion marking it as a question, but Sherlock in myself told me to let's investigate first and at last I found a solution too. Of course I'm curious about your experience and advices, but sure I would like also to share with you my findings.

So the question was, whether ACS servlet can serve contents with the "Content-Disposition" header. You may know, that without it, browser only displays the content inline/embedded, or if you are asked to save it the file gets a "fake" name, like "ACS.pdf". And of course nobody likes that, the customer wants to see the real filename (object_name) while opening an ACS url (we are using DFS, so this is the best way to put the content to the user).

I have not found anything in documentations how to solve this. Before we made this work by making a servlet on application server and we were streaming the content through it just to set this header. But after a little research, I've found out that there is an undocumented feature, which allows us to set any HTTP Response header in the result which ACS servlet will give you.

So if you have an ACS URL like

http://192.168.0.1:9080/ACS/servlet/ACS?command=read&version=2.0&docbase id=...&length=258&parallel_streaming=true

and if you append this request parameter

transient=Content-Disposition::attachment;%20filename=MyFile.pdf

then voilá, you got the content with proper file name offered!

My only worries are whether is this solution future/upgrade proof - as it is not a documented feature.

Does anybody have a better solution? For example is there/will be there a DFC API call (and meantime DFS) parameter which will do the same thing?