You would probably have better luck in an IIS group, but here it goes
anyway...

Have you considered making the PDF file accessible via the site so that it
can be fetched via an HTTPS address?  If you're dealing with a small number
of fairly static files, copying the files to your site might be the best
approach.  If there are a large number of files to be referenced and/or they
change often, you might want to consider setting up a virtual directory in
your web application to point through to a share on the other server.  This
should allow you to create links that point to the virtual directory over
HTTPS, avoiding the client-side problem entirely.  If you decide to go this
route, you should take a look at http://support.microsoft.com/kb/280383 for
some of the potential gotchas.

HTH,
Nicole

Think of what would be possible if you could do this:

I create a website that requests that a user create a login.  Their user
name and password are entered on an SSL site, but then on the next page I
redirect them to a site that's not accessable via HTTPS.  Additionally my
site also programatically disables that dialog box.  Now, the user is
entering personal information, thinking that it's safe, when in fact it
isn't.

Granted the above is a pretty strange scenario, but the point is the same.  
If you could do this, it would be an enormous security hole in the browser.

-Shawn
http://blogs.msdn.com/shawnfa  
--  
This posting is provided "AS IS" with no warranties, and confers no rights.


Note:  
For the benefit of the community-at-large, all responses to this message
are best directed to the newsgroup/thread from which they originated.
--------------------