# Best practice to prevent image hotlinking?

**URL:** <https://meta.discourse.org/t/best-practice-to-prevent-image-hotlinking/80814>\
**Category:** Product Support\
**Created:** [February 17, 2018, 11:51am UTC](https://meta.discourse.org/t/best-practice-to-prevent-image-hotlinking/80814 "2018-02-17T11:51:18Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![notriddle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/notriddle/32/133055_2.png) [@notriddle](https://meta.discourse.org/u/notriddle)\
**Post date:** [February 19, 2018, 1:43am UTC](https://meta.discourse.org/t/best-practice-to-prevent-image-hotlinking/80814/5 "2018-02-19T01:43:24Z")

</div>

> [@rdyar](#):
>
> Interesting that it looks like Referer is mis-spelled but that is working code.

> **[HTTP referer | Etymology](https://en.wikipedia.org/wiki/HTTP_referer#Etymology)**
>
> The misspelling of referrer was introduced in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the "Referer" header field into the HTTP specification. The misspelling was set in stone by the time (May 1996) of its incorporation into the Request for Comments standards document RFC 1945 (which "reflects common usage of the protocol referred to as 'HTTP/1.0'" at that time); document co-author Roy Fielding remarked in March 1995 that "neither one (referer or re When vis...

---

_[View the full topic](https://meta.discourse.org/t/best-practice-to-prevent-image-hotlinking/80814)._