|
Hi Rick,
the apache config tells the browser where to find the file, not windows networking.
You're right, sorry about that. One of your examples started the path with two leading slashes (//webdirectory/pdfs/mypdffilename.pdf), and that confused me, but you're right, unless it was accessed as a file: URI, this wouldn't be interpreted as Windows networking, since it's part of a relative link.
However, it's still just a link to the document. A Location: header would do the same thing without Javascript.
I thought Jim wanted to send the PDF/HTML document directly from his CGI program without providing a link to it. For example, if you wanted to use the program to secure the document, you wouldn't want there to be any way that a user can link directly to it, you'd want to require access to only be done through the program.
What I don't understand, however, is why you'd write it to the IFS at all. But perhaps I'm dwelling too much on that point, and should be demonstrating the solution instead of dwelling on "why IFS".
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
