yes, that helps with some proxies but not for all those web proxies around here

I solved the problem above, u can disregard it.

However, a suggestion for finding the user’s IP.

As you probably already know, finding an IP doesn’ always work, the user could be behind a proxy for example. Or maybe they have a dynamic IP. You could instead use this to find the IP:

if(isset($_SERVER['HTTP_X_FORWARDED_FOR'])) {
$ip = $_SERVER[’HTTP_X_FORWARDED_FOR’];
} else {
$ip = $_SERVER[’REMOTE_ADDR’];
}

Obviously it’s not foolproof, but it does work.

Better than this would be to log both IP addresses associated with the one download, and limit it that way.

please post your questions here.

Assume this is done; then obviously if they download the same file over and over, it will still be added to the overall transfer bandwidth. So if I was to leave the file ‘downloaded’ record intact (in the MYSQL database), how would I then allow the same user (identified by IP) to download the same file over and over, without it being added to their bandwidth? What I mean is, if the connection somehow times out for a file they are downloading, how can I allow them to try download it again (without increasing their IP’s overall bandwidth transfer)?

Also, has anyone any idea on how I could store IP addresses in a textfile as opposed to a database, for increased speed (or reduced load on the server - but could this pose a security risk)?

cheers!

The direct output is one way, used the symlinks too and just used a script to register the “access data” in the database.