zlacker

[parent] [thread] 3 comments
1. neilv+(OP)[view] [source] 2024-06-28 23:47:48
There are a bunch of settings in Firefox that affect this (if you don't mind occasionally breaking a Web site in a way no one will bother to diagnose): https://wiki.mozilla.org/Security/Referrer
replies(2): >>hinkle+T1 >>lizkno+J7
2. hinkle+T1[view] [source] 2024-06-29 00:06:18
>>neilv+(OP)
Just copy the url and paste it into a new tab.
replies(1): >>neilv+L4
◧◩
3. neilv+L4[view] [source] [discussion] 2024-06-29 00:37:18
>>hinkle+T1
That works for viewing a particular page.

Why people might want to adjust the `Referer` behavior of the browser is that it leaks more information than you might think.

4. lizkno+J7[view] [source] 2024-06-29 01:11:38
>>neilv+(OP)
They spelled it "correctly" there.

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.[7][8] The misspelling was set in stone by the time (May 1996) of its incorporation into the Request for Comments standards document RFC 1945[9] (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 referrer) is understood by" the standard Unix spell checker of the period.[10] "Referer" has since become a widely used spelling in the industry when discussing HTTP referrers; usage of the misspelling is not universal, though, as the correct spelling "referrer" is used in some web specifications such as the Referrer-Policy HTTP header or the Document Object Model.[3]

[go to top]