Hi Alex,

I think all it needs is to update the httpHeader variable assignment to look
like the following:

<@assign name="httpHeader" scope="request" value="HTTP/1.1 <@HTTPSTATUSCODE>
<@HTTPREASONPHRASE><@CRLF>Content-Type: <@var
local$resultSet[1,filename]><@CRLF>Content-Length: <@var
local$resultSet[1,filesize]><@CRLF>Content-Disposition: attachment;
filename=<@DQ><@var
local$resultSet[1,filename]><@DQ><@CRLF><@userreferencecookie><@CRLF>">

Hope that is what you're looking for.

~~~~~~~~~~~~~~~~~~~~~~~~~~~
Scott Cadillac,
Xmlx Software

[EMAIL PROTECTED]
(403) 254-5002 
http://www.xmlx.net/

XML-Extranet
P.O. Box 69006
RPO Bridlewood SW
Calgary, Alberta
Canada T2Y 4T9
~~~~~~~~~~~~~~~~~~~~~~~~~~~
   

> -----Original Message-----
> From: Alex Smersi [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, October 25, 2006 1:39 AM
> To: [email protected]
> Subject: Witango-Talk: Secure download and http header manipulation
> 
> Hello --
> I'm search to implement a secure download, where a specific .taf
> (downloadfile.taf) read specific file from a directory with no public
> read permission and give the end-user [in transparent manner] the
> faculty to save it on local; 
> I'm believe that Scott Cadillac's attached file [2001-based] is right
> to me, but how can I adapt it to run in WiTango v5.5 environment?
> 
> The download manager application can download .zip, .pdf and .txt
> files.
> Size of single file can vary between 35 bytes and 5/6Mb.
> 
> My environment is:
> - Windows 2003 box with IIS
> - WiTango server v5.5.x
> 
> I'm sure that http header is keyword here, but my knowledge about
> manipulation of http header is limted; anyone can suggest me 
> a previous
> thread where can I find appropriate info?
> Many thanks, Alex/
> 
> ______________________________________________________________
> __________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
> 

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to