Paul Pedersen wrote:
> "Andy Ruddock" <andy.ruddock+news@gmail.com> wrote in message
> news:47a790de$1@proxy.mimer.no...
>>>> Bottomline is nobody can type something like this:
>>>> http://www.example.com/~paul/secretfile
>>>> and access the file.
>>>
>>> Yes, that's what I meant.
>>>
>>> Although I am running Apache locally for test and development purposes,
>>> that
>>> is not where the site is hosted. It's hosted on a remote shared server
>>> running Apache, and I don't think I have a way to put a directory
>>> "outside"
>>> documentroot in that situation.
>>>
>>> I know that's not strictly an Apache issue, but if you have an answer,
>>> I'd
>>> be glad to hear it.
>>>
>> That depends on the configuration at the webhost. I use one where I have
>> access via ftp & ssh to place files outside documentroot.
>> ftp & ssh into $HOME, documentroot is $HOME/public_html
>>
>
> With mine, it "appears" that the main directory IS documentroot and I cannot
> change it.
> Instead, I can create directories within that, and prevent Apache from
> making those accessible except by my own scripts.
>
> Is that possibly the case, or am I misunderstanding something? If it
> matters, I think they are using Apache 1.x.
>

It's quite possible that your hoster has set up apache in this fashion,
in which case you'll probably have to use .htaccess to prevent the files
simply being delivered in response to a direct request via http.
Again, what you can achieve in this way is dependent upon the
configuration at your webhost.

--
Andy Ruddock
------------
andy_DOT_ruddock_AT_gmail_DOT_com (GPG Key ID 0x74F41E8F)