Scott,
The generic method is setting Content-type/Content-Disposition headers.
The extra path approach is a work around to the different behaviours of
the different browsers. Both IE and Netscape, under differend
circunstances, ignore those headers. (I don't remember the exact
circunstances, though.)
Some things that have been said (please search the archives, these are
only hints):
<use|don't use> the extra path
Content-type: your/content-type; name="your.file.name" (or filename=,
can't remember)
Content-Disposition: attachment; filename="your.file.name"
Content-Disposition: inline; filename="your.file.name"
Try using combinations of these, with your browser(s) of choice. I
suggest testing on both Netscape and IE, versions 3.0 and up.
Sorry if i'm suggesting more work then solutions ;-)
[]'s
Gatto
Scott Neufeld wrote:
>
> I could determine the filename in advance, but I think there should be some more
> generic approach -- there are certainly situations where it won't be possible to
> determine the filename in advance, and then I'll have to do something kludgey like
> perform a URL rewrite, appending the extra path info. Does the setHeader call not
> work because it isn't supported by the browser? I'm working with 4.5 of
> Communicator.
begin:vcard
n:Gatto;Rog�rio
tel;fax:+55 19 451 6300
tel;home:+55 19 237 0213
tel;work:+55 19 451 6300
x-mozilla-html:FALSE
url:http://www.widesoft.com.br
org:WideSoft Sistemas Ltda;Development
version:2.1
email;internet:[EMAIL PROTECTED]
title:Systems Analyst
adr;quoted-printable:;;R. Dr. Quirino, 1001 ap 62=0D=0ACentro;Campinas;SP;13015081;Brazil
fn:Rog�rio Meneguelli Gatto
end:vcard
