Glenn,

  I ran into this problem a while ago when I setup the
sambaix.com site and introduced the download section.  The
way I worked around it was to include the name of the file
to be downloaded "following" the actual page name in the
URL, but before the URL parameters.  For example:

http://www.somedomain.someorg/program.ext/filename.pdf?key=abc123

This may not work with all web servers, (it seems like IIS wanted
some slight variation of the above to work correctly).  The server
correctly parses out the page name (program.ext) as well as the
URL parameter (key=abc123) and passes the name following the template
name back as the name of the file to download (filename.pdf).



  This is just one of the many "fun" things that you have to deal
with when supporting different browsers.  I envy web programmers
on Intranet's where they can define a single "standard" browser
for their customers to use.

Regards,
Michael L Gueterman
Easy (sometimes :) Does It Technologies
http://www.editcorp.com
voice: (888) 858-EDIT -or- (573) 368-5478
fax:   (573) 368-5479
--

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of COLE,GLENN (Non-HP-SantaClara,ex2)
> Sent: Wednesday, March 01, 2000 4:15 PM
> To: [log in to unmask]
> Subject: [HP3000-L] OT: HTTP question
>
>
> I have a CGI that is invoked by a web user to retrieve an
> Acrobat PDF file, but I'm not happy with the results.
>
> The URL looks something like
>
>    http://.../getdoc.cgi?key=abc123
>
<snip>