Subject:
Re: [PHP] Re: alternative to protecting files through http auth.
From:
Jason Wong [EMAIL PROTECTED]
Date:
Sat, 17 Jan 2004 05:08:29 +0800
To:
[EMAIL PROTECTED]
On Saturday 17 January 2004 04:03, Scott Taylor wrote:
Alternately, if you aren't able to create directories or access files
On 18 [EMAIL PROTECTED] 2004 01:59, Scott Taylor wrote:
Yes, sorry. Here is the code: $file =
'http://miningstocks.com/protected/archive/Dec03PostPress.pdf'; //now
view the PDF file header(Content-Type: application/pdf);
header(Accept-Ranges: bytes); header(Content-Length:
Paul Chvostek wrote:
On Wed, Jan 14, 2004 at 04:17:06PM -0500, Scott Taylor wrote:
Is there no other way to protect your (non PHP) files than through
authentication? I've been trying to set up a system that will protect
files. Those trying to access the files would only be able to do so
On Saturday 17 January 2004 04:03, Scott Taylor wrote:
Alternately, if you aren't able to create directories or access files
outside the DocumentRoot for your site, you can create an unbrowsable
storage directory protected with a .htaccess file. If the filesystem
permissions are correct,
On Wed, Jan 14, 2004 at 04:17:06PM -0500, Scott Taylor wrote:
Is there no other way to protect your (non PHP) files than through
authentication? I've been trying to set up a system that will protect
files. Those trying to access the files would only be able to do so
after entering their
there has been a discussion in this group recently about URL re-writing (see
URL rewriting...anybody done this? and replies)
That is a possibility, using a combination of
URL Re-Writing
PHP Sessions/Cookies
And the Location: header
So all requests go back to the index, then you decide from the
Paul Chvostek wrote:
On Wed, Jan 14, 2004 at 04:17:06PM -0500, Scott Taylor wrote:
Is there no other way to protect your (non PHP) files than through
authentication? I've been trying to set up a system that will protect
files. Those trying to access the files would only be able to do so
7 matches
Mail list logo
