forcing ie to save the contents of the html instead of displaying it

[Julie]

I have an html file where I display name,address,zip. It is one per line so
it is basicall a list of addresses.

But I would like ie6 to force the download prompt of this long list of names
instead of displaying it to their browsers. This way they can save the list
to a file. I know I can set it up as a txt file and let them download it
that way, but right now this file is generated from a source program which I
have no control over and it creates this .html file.

I looked around google and found a few things to try like:
<meta http-equiv="content-type","application/download">

<meta http-equiv="content-type","application/force-download">

<meta http-equiv="content-type","application/octet-stream">

<meta http-equiv="content-disposition","attachment; filename=list.txt">

but these dont seem to work at all.

Thanks for your help.

[David Dorward]

Julie wrote:

<meta http-equiv="content-type","application/download">
<meta http-equiv="content-type","application/force-download">
<meta http-equiv="content-type","application/octet-stream">
<meta http-equiv="content-disposition","attachment; filename=list.txt">

http-equiv is a joke, it can't be equivalent to most http headers since the
browser has to act on them before starting to handle the body of the http
response. If they are in the body, then its too late.

Use real http headers (how you do that depends on your server and/or server
side programming language), and use content-disposition (rather they lying
about the content type).

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

[Eric Kenneth Bustad]

In article <LU*****************@newsread2.news.atl.earthlink. net>,
Julie <ju****@optonline.net> wrote:

I have an html file where I display name,address,zip. It is one per line so
it is basicall a list of addresses.

But I would like ie6 to force the download prompt of this long list of names
instead of displaying it to their browsers. This way they can save the list
to a file. I know I can set it up as a txt file and let them download it
that way, but right now this file is generated from a source program which I
have no control over and it creates this .html file.

I looked around google and found a few things to try like:
<meta http-equiv="content-type","application/download">

<meta http-equiv="content-type","application/force-download">

<meta http-equiv="content-type","application/octet-stream">

<meta http-equiv="content-disposition","attachment; filename=list.txt">

but these dont seem to work at all.

Thanks for your help.

Why *force* them to download it? Certainly they can get their browser
to do this if *they* want it to without any special work on your part?
Or does ie6 not have this capability?

--
= Eric Bustad, Norwegian bachelor programmer

[Alan J. Flavell]

On Fri, 9 Sep 2005, David Dorward wrote:

Use real http headers (how you do that depends on your server and/or
server side programming language),
Indeed...
and use content-disposition (rather they lying about the content
type).

As a background remark, though: RFC2616 warns that the use of this
header has serious security implications: in earlier times it was
customary for HTTP user agents to disregard any such header. But as
time went by, the header was implemented in MSIE as well as in web
browsers (sometimes with adequate user protections).

http://www.w3.org/Protocols/rfc2616/...5.html#sec15.5

The original idea of the interworking protocols was that it was the
*recipient's* business to decide whether they wanted to render a
resource or to download it. The suthor/publisher's job was just to
advertise its content-type honestly (as you note). The idea of a
mischievous author proposing a download, to some sensitive file on the
recipient's system, and the naive user acceding to the request, is
just too attractive to a certain kind of pondlife on the 'net.

Re: the subject line: generally speaking, "force" does not work, on
the WWW. And it's good that it is so. h t h