[users@httpd] Apache trick to protect the Helix Basic Serer

[lou loui <lj...@hotmail.com>]

Two ips, one server (running Apache 2 on https:443 and Helix Basic http:80).
Who is protect the Helix Basic media content and How?

Access to the media is given by an url link on the site, but an user can 
then take the address and play the media connecting directly with the Helix 
Basic server. The link alias will change every day so I get a little 
protection, but its not enough.

I can play with whatever Linux or Apache authentication feature, my users 
are stored in a mysql database in wich I could put the ip adress of the user 
(php), what would be the best way to do this?

Any of these brainstormed ideas would possibly work.

1. use Apache mod_access to filter access to directory with media content. 
would'nt it interfere with the Helix Basic if both listen to port 80?

2. use Apache mod_rewrite and the fact that Helix can be restricted to 
listen to ip#2(port:80) only to redirect media request made to ip#1 to ip#2.

3. use a Helix Basic authentication feature that I did not find yet.

4. Use an linux feature to check access to videos made by the Helix server, 
and check the database to see if ip address is allowed to connect.

So as you can see, I really need a tip on this.

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org