Skip site navigation (1) Skip section navigation (2)

Re: Storing Large Objects

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: brew(at)theMode(dot)com
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Storing Large Objects
Date: 2005-04-18 15:21:18
Message-ID: 20050418152118.GA22606@wolff.to (view raw or flat)
Thread:
Lists: pgsql-novicepgsql-performance
On Mon, Apr 18, 2005 at 02:09:10 -0400,
  brew(at)theMode(dot)com wrote:
> 
> Since I've heard large objects were a bother I've written it so the mp3s
> were in files with long obfuscated filenames and have put them in a
> directory hidden behind basic authentication, planning a php front end to
> the basic authentication and storing the file urls in the database.  Now
> I'm considering shortlived symbolic filenames to further make it difficult
> to rip off the mp3 files by other users with valid log in credentials that
> can get past the basic authentication.

Why not put the files somewhere where only the application can get at them
instead of under the document root. That way they have to compromise your
application to get at them. No amount of url guessing will give direct
access.

In response to

Responses

pgsql-novice by date

Next:From: Sean DavisDate: 2005-04-18 15:39:21
Subject: Re: PostgreSQL Guide for Oracle Users?
Previous:From: vladimirDate: 2005-04-18 15:18:23
Subject: Re: Migration of postgres 7.3 to postgres 7.4 from one server to another server

pgsql-performance by date

Next:From: Andrei GasparDate: 2005-04-18 15:36:14
Subject: Sort and index
Previous:From: Dave HeldDate: 2005-04-18 15:20:36
Subject: Re: How to improve db performance with $7K?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group