News for hackers. Stuff that matters.
Re:The story, as best I can remember, of the origin of Mosai... by lizknope on Friday June 28, 2024 @06:42PM (#40826104)
That's kind of hilarious. I guess he's using the HTTP "referer" tag
Re:The story, as best I can remember, of the origin of Mosai... by neilv on Friday June 28, 2024 @07:47PM (#40826593)
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
Re:The story, as best I can remember, of the origin of Mosai... by hinkley on Friday June 28, 2024 @08:06PM (#40826710)
Just copy the url and paste it into a new tab.
Re:The story, as best I can remember, of the origin of Mosai... by neilv on Friday June 28, 2024 @08:37PM (#40826888)
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.

Re:The story, as best I can remember, of the origin of Mosai... by lizknope on Friday June 28, 2024 @09:11PM (#40827072)
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]