Guten Tag Randolf Richardson,
am Dienstag, 20. August 2019 um 19:06 schrieben Sie:
> One of the great things about Perl is that there is more than one
> way to do things, and this flows through to how to handle the storing
> and retrieving of images. (Everyone else is welcome to share
In answer to your question, I recognize that there are many pros and
cons to storing images in PostgreSQL. I'm providing a fuller answer
here and including it in the ModPerl mailing list in the hopes that
it will be helpful in some way to others who are considering this...
Yes, you can use a Perl handler to do that. (I do this to send
images stored in PostgreSQL that are retrieved with DBI instead of
reading from files on the file system outside of the document root.)
Perl can read X number of bytes into a local variable, then send the
contents
1. Streaming in chunks has nothing to do with security - you should have
proper authentication and authorization layer wrapping these requests.
2. Handling chunks and large files are things which apache has perfected
and we usually let apache do the nitty gritty.
After all the validations are
You could put the files behind Nginx and use your mod_perl web app as an
external authentication service. I've never done it but it doesn't look too
hard.
On Fri, Aug 16, 2019, 12:25 PM John Dunlap wrote:
> In Java servlets, I can stream a file back to the browser one chunk at a
> time. This
One fairly straight-forward approach would be to write a script that
serves as the path for downloads, then have it parse the filename to
use as a key in determining which content to send to the user. (The
AcceptPathInfo directive could be helpful for this, especially if you
want to
In Java servlets, I can stream a file back to the browser one chunk at a
time. This has 2 benefits which interest me.
1) Files can be stored outside the web root so users cannot download them
unless they are logged in, even if they know the path.
2) Large files can be streamed back to the client
