Fun protocol fact: the HTTP header which contains the referring url is called "referer" because the developer spelled "referrer" wrong and nobody noticed, so it made it into the official standards and now it's ossified.

Replies (21)

Protocol ossification lore
Jameson Lopp's avatar Jameson Lopp
Fun protocol fact: the HTTP header which contains the referring url is called "referer" because the developer spelled "referrer" wrong and nobody noticed, so it made it into the official standards and now it's ossified.
View quoted note →
jb55's avatar
jb55 _@jb55.com 7 months ago
lets just update the dictionary and pretend nothing happened
i saw a note about this in some http spec documentation the other day. there's a bunch of other funny things in the protocol that you can find. one of the most troublesome that has only just recently started to get fixed is the Forwarded headers now are finally part of the spec. which actually means that you now have to write more code to handle the X-Forwarded-* as well as the Forwarded-* headers to parse out the client origin IP address
Fun Javascript wtf. Comments in Javascript are usually written with "//", but you can also write them with "<!--", because devs thought it should be compatible with HTML comments. So you can have a variable x, calculate --x, negate the result with !--x, and calculate: y = "wat"<!--x Only to have y === "wat". Works in Node.js too.
Somebody needs to immediately notify the Oxford English Dictionary that the spelling has changed forever
Jameson Lopp's avatar Jameson Lopp
Fun protocol fact: the HTTP header which contains the referring url is called "referer" because the developer spelled "referrer" wrong and nobody noticed, so it made it into the official standards and now it's ossified.
View quoted note →
Really?! This closes a tremendous gap in my brain: I spent years fighting mentally every time I had to write this word in a non header context, but I was too lazy to check a dictionary. You saved a lot of my precious future time, thanks!