Is there some easy way to protect PDF (and perhaps other kinds of documents)
from sideaways access?
In other words, after building login pages, protecting html/cfm pages from
direct access, etc.; someone can still directly access a document with a direct
URL, like
www.xxx.com/.pdf
Any qu
> Is there some easy way to protect PDF (and perhaps other kinds of documents)
> from sideaways access?
>
> In other words, after building login pages, protecting html/cfm pages from
> direct access, etc.; someone can still directly access a
> document with a direct URL, like
>
> www.xxx.com/yyy
Keep them off the webroot, and then serve them up with or apache
mod_xsendfile
Mark
On Tue, May 4, 2010 at 8:57 AM, col...@uci.edu col...@uci.edu <
col...@uci.edu> wrote:
>
> Is there some easy way to protect PDF (and perhaps other kinds of
> documents) from sideaways access?
>
> In other word
Store them outside your web root and serve them up with cfcontent. Just
remember a CF thread is used for the duration of the download.
~Brad
Original Message
Subject: How to protect PDF documents from direct access
From: "col...@uci.edu col...@uci.edu"
Date: M
I am on a shared host, so moving outside the web directories is not
practical.
On 5/3/2010 4:09 PM, Dave Watts wrote:
>
>> Is there some easy way to protect PDF (and perhaps other kinds of documents)
>> from sideaways access?
>>
>> In other words, after building login pages, protecting html
Rename them with a .cfm extension - put a Application.cfm in the root of the
dir with a in it.
Then push them out through and using HTTP Headers tell the
browser the name of the file without the .cfm extension.
Mark
On Tue, May 4, 2010 at 12:53 PM, Rick Colman wrote:
>
> I am on a shared ho
...or I could also say ;o) get off a shared host.
Mark
On Tue, May 4, 2010 at 1:00 PM, Mark Mandel wrote:
> Rename them with a .cfm extension - put a Application.cfm in the root of
> the dir with a in it.
>
> Then push them out through and using HTTP Headers tell the
> browser the name of th
On 5/4/2010 10:01 AM, Mark Mandel wrote:
>
> ...or I could also say ;o) get off a shared host.
actually a decent shared host should provide a dir w/your web root under that.
i
mean where would people put their access databases ;-)
~~~
8 matches
Mail list logo
