Forum Moderators: phranque
1- i already have agent blocking....but as im sure you're aware they caught onto this along time ago,and most programs spoof their agent to a standard browser...
2- im not sure what you mean by this....if you mean to hide the real path to the file, then thats not very practical if you have lots of files, and their paths already posted on your website....as for limiting connection by ip...most of my users are behind proxies...so that wont be very good....
isnt there another way to do this? perhaps a limit on the number of connections to certain mime types, or per user session etc?
thanks
I have no idea what your site is like, so back to fundamentals:
List out the reliable information you do have about each user, be that user-agent, IP address, session ID, cookie(s), X_FORWARDED_FOR proxy headers, etc.
Then devise a script to track each user based on that information and limit the number of connections for that user to some number per unit time.
If you have no reliable per-user information, then your only option is a blanket bandwidth limitation or access limitations on a per-file basis -- both of which are 'unfair' to your users who are not abusing your server (since all users will be limited with this kind of approach).
Jim