in reply to Sending an image to a browser

Hello,
I don't know for sure, but it you are trying to stop people from using your images from another server, isn't there something you can do with a .htaccess file. I haven't done it myself, but you can be pretty strict about what is and isn't allowed to be requested from your server. So that route might be worth investigating...

Tom

Learning without thought is labor lost; thought without learning is perilous. - Confucius
WebChalkboard.com | For the love of art...

Replies are listed 'Best First'.
Re^2: Sending an image to a browser
by dorward (Curate) on Apr 19, 2005 at 16:43 UTC

    The specifics can be seen at http://www.allmyfaqs.com/faq.pl?Prevent_bandwidth_theft, but note that this will also block the images for users of certain privacy protecting proxies (although only ones which break the HTTP specification by replacing the Referer header with something invalid rather then removing it entirely)

Re^2: Sending an image to a browser
by chas (Priest) on Apr 19, 2005 at 11:17 UTC
    But then won't everyone have to enter a username and password to see the image (even when it's produced by the cgi)? This doesn't seem to be what the OP wanted.
    chas
    (Update: My error; the answer is "no".)

      I think you misunderstand the purpose of the .htaccess file - which is, simply put, to provide a per directory configuration. Please see the apache documentation if this is not clear.

      /J\