W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1996

content-disposition header

From: Larry Masinter <masinter@parc.xerox.com>
Date: Wed, 9 Oct 1996 01:51:01 PDT
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Cc: sdorner@qualcomm.com, rens@century.com
Message-Id: <96Oct9.015101pdt."2759"@golden.parc.xerox.com>
Should content-disposition from RFC 1806 be considered for HTTP?

------- Start of forwarded message -------
Date: Tue, 8 Oct 1996 04:38:10 PDT
From: Michael Naumann - ESO Garching +49 89 32006 430 <mnaumann@eso.org>
Organization: European Southern Observatory, Garching
To: www-talk@w3.org
Subject: Re: [Q] Changing default name in a FORM
References: <199610080948.LAA26948@beatles.cselt.stet.it>

Maurizio Codogno wrote:
> I have a script which selects a file and send it to the user. It
> is accessed via a form, with action POST.
> Unfortunately, the file is sent with the form's name as default name,
> and the user should rename it by hand.
> 
> Does HTTP/1.0 have any header line which can be used to overcome it?

Try sending 

  Content-type:        application/octet-stream
  Content-Disposition: attachment; filename="fname.ext"

HTTP header fields in the response of your script. This
at least works with Netscape Navigator since version 2.0

Although not specified in the HTTP 1.0/1.1 drafts the
the definition of Content-Disposition: can be found in 
http://www.internic.net/rfc/rfc1806.txt

<michael

-- 
** Michael Naumann * ESO * mnaumann@eso.org 
** http://www.eso.org/~mnaumann/


------- End of forwarded message -------
Received on Wednesday, 9 October 1996 01:56:02 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:14 EDT