Received: from cr322781-a.ym1.on.wave.home.com (cr322781-a.ym1.on.wave.home.com [24.112.37.89]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f07Hc2B23146 for ; Sun, 7 Jan 2001 12:38:02 -0500 (EST) (envelope-from svanegmond@bang.dhs.org) Received: from svanegmond by cr322781-a.ym1.on.wave.home.com with local (Exim 3.20 #1 (Debian)) id 14FJp3-0005a3-00; Sun, 07 Jan 2001 12:41:37 -0500 Date: Sun, 7 Jan 2001 12:41:37 -0500 To: Louis Bertrand Cc: pgsql-php@postgresql.org Subject: Re: download binary files to browser Message-ID: <20010107124137.C21271@bang.dhs.org> Reply-To: svanegmond@home.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from louis@bertrandtech.on.ca on Sun, Jan 07, 2001 at 12:36:31PM -0500 From: Stephen van Egmond X-Archive-Number: 200101/17 X-Sequence-Number: 82 Louis Bertrand (louis@bertrandtech.on.ca) wrote: > What headers can I send to fill in that file name? Look at content-disposition in the HTTP RFC. I do this in a similar application: header("Content-Disposition: attachment; filename=\"$original_name\""); it helps on the end-user side if you also report the correct MIME type for the document (i.e. application/msword). header("Content-type: $mime");