3 ms·
Your solution wouldn't help: my browser would still request the image from your server, and you'd have to send me at least the headers. That in itself could kil
by IgorPartola 12y ago
Your solution wouldn't help: my browser would still request the image from your server, and you'd have to send me at least the headers. That in itself could kill your traffic cap. Instead, my request should send you the domain on which I want to display the image, and then you can give me a 400 error.
- icebraining 12y agoInstead, my request should send you the domain on which I want to display the image, and then you can give me a 400 error. But that tells me that a browser with a certain IP, user-agent and possibly even cookie ID is accessing a certain third-party site. I shouldn't have that information just because my image was hotlinked in that site. And while my solution does still consume traffic, the idea would be discouraging the hotlinking in the first place. Why would anyone keep my image hotlinked if it didn't work?