Ethan
Julia's Reruns Bothow URLs work
Heath Borders@b0rk_reruns great stuff! Path parameters are a little-known and little-used URL quirk. I see ads libraries use them sometimes.
BenBE@b0rk_reruns missing the username:password@ part in front of the host …
🇨🇦 D'Arcy Norman@b0rk_reruns @gruber it’s missing the username/password part, showcased by the fun .zip and .mov domain tricks.
Carlos Eŭgenĭo@b0rk_reruns The protocol ends at the colon: "http:", "https:", "ftp:", "mailto:". The double slash means that it is followed by the identification of a server or authority, in this case the server is identified by a domain name. If no server is referred the URL doesn't include the double slash: mailto:[email protected]
robrykDo you know why `file:` always specifies an empty server?
Piers Cawley
ay@b0rk_reruns Need a special edition for query string where to explain what utm_source, utm_medium, fbclid etc. do and that it is perfectly OK not to drag them along when sharing a link 😏.
Fubaroque@b0rk_reruns A fragment refers to the name attribute of an anchor tag. Not the id.
Fabio Tavano@b0rk_reruns I think something is missing here 😉 isn’t it @jschauma ?
Jim Luther@b0rk_reruns This is not entirely correct, but is probably better that what 99% of the developers I’ve worked with think a URL/URI is. I’m still scarred from trying to fix the incorrect URL parsing code at Apple.
mika 
:verif@b0rk_reruns i misread this as "how girls work" and i thought it was one of the most glorious shitposts
Alex White@b0rk_reruns This is fabulous. Is there any reason why the username:password@ which can exist between the https:// and the domain isn’t included? Is it just that it is very rare nowadays?
I had forgotten about it, then saw it mentioned in a ‘zip’ domain hijack route.
Cheers @b0rk
Julia Evans@PlaneSailingGames @b0rk_reruns just didn't think of it
Cassandrich@b0rk_reruns Just came across this and I love the idea of a "reruns bot".
Jolan@b0rk_reruns the name=value separated by & part is the recommend way to encode nowadays but it’s not part of the url spec. One could write a server which handle value:name separated by / and that would be an equally valid url.
; was an alternative recommended separator but it is not anymore.
; was an alternative recommended separator but it is not anymore.
MatthiasPortzel@b0rk_reruns Nothing against Evans, this is a great practical guide. But I hate that due to the complexity of modern software there are like 3/4 things that this oversimplifies. Missing username:password and segment, and URL encoding is optional except for characters that have other meaning in a URL path (?, &, #). You could include space and @ in a URL path if you wanted, most people just don’t. (I’m going off of things I’ve seen in the wild, I haven’t read the spec.)
Trond Olsen@b0rk_reruns I really enjoy these neat and tidy infographics. Little room for confusion - unless nitpicking.
Username/password in urls has been bad security practice for a long time now. According to the URI spec [https://datatracker.ietf.org/doc/html/rfc3986/#section-3.2.1] it has been deprecated since 2004.
Love to see more on networking like ipv4 cidr subnetting, or even ipv6 which still confuses me.
RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]
Sandor Szücs@b0rk_reruns the host header should be Host: examplecat.com, not example.com :)
Dag Øien@b0rk_reruns missing DNS-hostnames, may be more than just the actual domain name, like images.example.com
Daniel Tucker@b0rk_reruns such a good infographic!
@b0rk_reruns Shouldn't the "domain" part actually be "host"?