this is not true. The two features are not related at all.
mmm, no.
That option is not well designed maybe, but it is supposed to be working.
did you try to enter your web server address as value for "allowed referer"?
Thanks for your reply!!
I've found a workaround by using event scripts! Thanks for the new feature!!
Here's my solution:
[download]
{.if not |{.header|Referer.}|{:{.disconnect.}:}.}
Since I noticed that by entering the url directly, the http request wouldn't have a referer at all. So with this script I can disconnect people if their request comes with no referer!!
Finally got it done!!
---------------------------------------------
Actually I've been trying to use different builds to test this "allowed referer" and found that hfs2.2f behaved differently from hfs2.3.
With the "allowed referer" set, the 2.2 build allows direct url accessing but blocks directory browsing (for example, it blocks "
http://192.168.10.10/", but it won't for "
http://192.168.10.10/file.jpg"), while 2.3 allows both.
So maybe you would like to check if this is a bug?
Anyway, thanks for the great software!! Love it!!!!!!!!!!! (though I've been upset by this problem for the past few days,
)
