Both. The files are currently stored on a file server that is not accessible via HTTP and are replicated over to the web server. I want to avoid the replication and the additional storage needs. Also, this is sensitive information that is currenly protected only by obsurity (it would be hard to guess at the URL.)
I do not fully understand what needs access to what, and when. If the web server itself has access to the files, but the directory/files are not directly HTTP-able in the browser, can I still serve the PDF as an embedded object? Or does the browser need to be able to reach the file directly in order to know how to display it as an embedded object?
Main Topics
Browse All Topics





by: FunkmotorPosted on 2007-06-22 at 08:36:46ID: 19342295
Sure, all you have to do is have your web server pull the files from wherever it is that your PDF files are stored. It will have to be accessible to the web server, and that might still make it vulnerable.
Do you want to do this for security reasons or just because the PDF library is somewhere else and you don't want to duplicate it?