Posted by J.O. Aho on 11/21/05 23:20

Freebird wrote:
>> You can limit access to a directory based on the ip that tries to access.
>>
>> <Location /download-specialfiles>
>> Order deny,allow
>> Deny from all
>> Allow from 192.168.0.1 10.0.20
>> </Location>
>
> Well, that wouldn't work because it works like this:
> the script is installe on server b, than, server b subscribe to a service in
> the server a.
> So, from server b, I connect to server a, register his domain, username and
> password, and next time the user from server b wants to use the service, the
> script will go form server b, verify if the domain from server b is ok, and
> if so, allow server b to do whatever it must be done.

So server B is "yours" which is the one that will manipulate server A after it
has been registered to your service on server B (this is how I understand your
description).

Run the registration over https (you need to enable that on server B's web
server program).

The server A will have to setup a directory which allows server B to access
server A, if your server don't have a static-ip, then subscribe to a DynDNS
service (there are loads of free ones) and use ip-name instead of ip-number.


> But if the server owner restarts his machine, he's ip will probably change,
> and the verification will not work ok, what do you think ?

Depends on what you want to do, I have a bit difficult to follow your reason.


//Aho

[Back to original message]