On Thu, Mar 20, 2003 at 02:04:55PM -0800, Andrew Ho wrote: > Hello, > > AF>As an aside, if anyone on the list knows of ways to defang this really > AF>annoying IE behavior, I would be most interested in knowing about it.... > > Two (and probably more) ways to do it. This is probably in a FAQ > somewhere as it is a common problem. > > (1) Fool IE by snarfing another extension in the URL. For example, instead > of requesting http://www.example.com/foo.pl, tack on a dummy parameter and > request http://www.example.com/foo.pl?filename=foo.txt. >
I don't think this works with everything. > (2) Send a Content-Disposition header. This is a MIME header and not in > the HTTP spec but IE respects it: > > Content-Disposition: inline; filename=foo.txt > I know that this doesn't work for all browsers. Our solution was to do a simple path info that was basically irrelevent. http://foo.bar.com/path/to/fetchfile.pl/foobar.pdf Every browser we tested it on tried to save the file as foobar.pdf. Rob
