>>>>> On Fri, 02 Jan 2026, Ionen Wolkens wrote: > On Thu, Jan 01, 2026 at 09:03:18PM +0500, zyxhere💭 wrote: >> Minor nitpick maybe don't have the trailing / so just >> https://www.gentoo.org looks better IMO
> Think that's suggestive, personally always prefer trailing / which > makes URLs clearer that they're not opening a path to a file but rather > opening a directory with whatever is default. Much like how e.g. > cd /usr/sh<tab> results in /usr/share/ > I think it also looks better in a opening/closing way together with > the https://. Somewhat more formal than "looks better", a normative reference for this would be RFC 3986 section 6.2.3 [1] which says: "In general, a URI that uses the generic syntax for authority with an empty path should be normalized to a path of '/'." > In general it'd be good to be consistent and use the same way > everywhere (incl. websites, etc...), albeit I imagine we have some of > both as-is and looking will be inconclusive. > os-release had the trailing / anyway, we may as well not introduce > changes here as it's not the goal of the eclass. > fwiw if I open https://www.gentoo.org w/o the trailing / with curl -v > or use my browser (qutebrowseR), the trailing / is automatically added > so I guess it may be the more "expected" way? > curl -v https://www.gentoo.org > * [HTTP/2] [1] OPENED stream for https://www.gentoo.org/ [1] https://www.rfc-editor.org/rfc/rfc3986#section-6.2.3
signature.asc
Description: PGP signature
