4 ms·
There are some legitimate (IMO) uses of referrers, though. Preventing hot-linking, for example.
by untog 13y ago
There are some legitimate (IMO) uses of referrers, though. Preventing hot-linking, for example.
- vidarh 13y agoThere's many legitimate uses for them, but while they're convenient for preventing hot linking, they're not necessary. Preventing hotlinking can be done easily enough by appending a url argument that changes regularly, and can be made performant by adding that argument checking to the configuration of your frontend/caching servers.
- laumars 13y agoNot a bad idea, but you could probably just use the session ID (or a unique ID linked to the users session if it's a secure site). So when the session expires, so does access to the content. The drawback to this is you're exponentially increasing DB i/o. Personally though, I'd rather not block hotlinking. But I understand why some people are against it.
- devicenull 13y agoIt's actually implemented in a better way (no db required) with most web servers: http://wiki.nginx.org/HttpSecureLinkModule http://wiki.nginx.org/HttpSecureLinkModule
- tomjen3 13y agoNo. The web is about links, if you don't want things to be linked too, don't make them accessible to the general public.
- krapp 13y agoYou can responsibly link to an image on someone else's server without embedding it directly on your site. The web is no longer just hypertext, and the potential inequity in resources and scalability between servers matters. Why should I be expected to suffer and pay for anyone who decides they like a particular image on my site and want to use it in their forum avi? They can just as easily copy it locally and use it.
- untog 13y agoMeanwhile, in the real world people have server bills to worry about.
- Silhouette 13y agoSpoken like someone who never got a large and surprising bandwidth bill because some jerk linked to a high value graphic on his site and then blogspammed every forum on the web to promote "his" content. The ability to effectively DOS anyone's site in this way, not to mention presenting their content as your own without technically infringing copyright (or so the Ninth Circuit seem to feel in the US, though courts in other jurisdictions have differed) is a genuine and, for the unfortunate victim, potentially very expensive problem with the current state of the web. Doing this has always been bad netiquette, but these days even Google do it, and indeed used the fact that they were doing it in their defence in one of the aforementioned copyright cases.
- derleth 13y agoSpoken like someone who's about to get goatse'd: http://ascii.textfiles.com/archives/1011 http://ascii.textfiles.com/archives/1011 (No goatse images on the page I directly linked to. It does link to them, but the links are marked.)