Closed (won't fix)
Project:
Image
Version:
5.x-1.x-dev
Component:
image.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
3 May 2007 at 16:54 UTC
Updated:
11 Jun 2024 at 12:23 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedFor some reason the domain name was filtered out. So here it is again with code tags.
http://somedomain.com/system/files/images/test.gifComment #2
Anonymous (not verified) commentedI just found out that I was not correct.
The hotlinkink prevention does work for attached files.
However, it does NOT work for image content types, the image can be directly accessed.
I am not sure whether this is a bug in the file system or a bug in the image module.
Comment #3
chx commentedComment #4
drewish commentedi'm marking this won't fix because it's not a bug. image and the core's file are working correctly. if you want to prevent hot linking you need to use apache's features to check the referer.
Comment #5
Anonymous (not verified) commentedI have always assumed that the private download method was designed for that matter.
It is rather confusing that regular attachments cannot be hotlinked when using private download method and images attached to image nodes do can be hotlinked.