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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice pgsql-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

Browse pgsql-novice by date

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

Browse pgsql-performance by date

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