Hello and welcome to our community! Is this your first visit?
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 5 of 5

Thread: htaccess:

  1. #1
    New Coder
    Join Date
    Jan 2006
    Thanked 0 Times in 0 Posts



    I've been trying to block a user by denying their IP addresses in an htaccess file. But I've recently noticed that this person has managed to view pages of my site via the German translation of Google. How can I completely block translations by Google or any other translation site ?
    And do I have to block all languages ? Or can I choose the ones that are allowed to translate pages of my site ?

    Thanks for any help !

  2. #2
    Supreme Master coder!
    Join Date
    Jun 2003
    Cottage Grove, Minnesota
    Thanked 1,168 Times in 1,159 Posts
    That's tough to control. What happens if that user accesses using
    someone else's computer? What is the reason for banning? Maybe you
    need to think outside the box (come up with something different).

  3. #3
    Master Coder
    Join Date
    Apr 2003
    in my house
    Thanked 201 Times in 197 Posts
    yeh as mlseim says, its tough to control who sees your pages if they use a different PC from their own.

    I reckon you might need to password protect those pages that you want to limit viewings of. Then, only those who you authorise can see them however, I don't know how you would identify this specific individual.


  4. #4
    Senior Coder CFMaBiSmAd's Avatar
    Join Date
    Oct 2006
    Denver, Colorado USA
    Thanked 506 Times in 494 Posts
    By going through a site like the Google translator, they are basically reading your page through a proxy/third party server. There are probably 10's of thousands of proxy servers on the Internet, each with their own IP address. It is also easy to obtain a new IP address if they did not want to go to the trouble of finding a different proxy server to use. So, banning IP addresses is not an effective method of limiting access to your content.

    What exactly are you trying to prevent? Hot linking of images, which uses your bandwidth? Or limiting access to content on some of your web pages?

    To stop hot linking, it is necessary to start a session on your web page and then dynamically output images only if the session exists. [Note: The reason I did not mention checking the HTTP_REFERER header is that every proxy script I have examined sets this to the URL being requested, so it looks like the REFERER is the site where the images are being fetched from.]

    To limit access, it is necessary to use email verified registration and login. This however, will only slow someone down, as it is easy to obtain any number of free email accounts that could be used to register with.
    Finding out HOW to do something is called research, i.e. keep searching until you find the answer. After you attempt to do something and cannot solve a problem with it yourself, would be when you ask others for help.

  5. #5
    Supreme Master coder! _Aerospace_Eng_'s Avatar
    Join Date
    Dec 2004
    In a place far, far away...
    Thanked 1,043 Times in 1,019 Posts
    Quote Originally Posted by CFMaBiSmAd View Post
    To stop hot linking, it is necessary to start a session on your web page and then dynamically output images only if the session exists.
    Wouldn't it be easier to use htaccess?


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts