--------\r
RFC 3986 talks about normalization, and it recommends adding a slash:\r
\r
-> In general, a URI that uses the generic syntax for authority with an\r
-> empty path should be normalized to a path of "/".\r
+ In general, a URI that uses the generic syntax for authority with an\r
+ empty path should be normalized to a path of "/".\r
\r
http://tools.ietf.org/html/rfc3986#section-6.2.3\r
\r
---------------\r
It also requires the slash after the domain name when serializing an URL:\r
\r
-> An absolute URL must be a scheme, followed by ":", followed by either a scheme-relative URL [...]\r
-> [...]\r
-> A scheme-relative URL must be "//", optionally followed by userinfo and "@", followed by a host, optionally followed by ":" and a port, optionally followed by an absolute-path-relative URL.\r
-> [...]\r
-> An absolute-path-relative URL must be "/", followed by a path-relative URL that does not start with "/".\r
+ An absolute URL must be a scheme, followed by ":", followed by either a scheme-relative URL [...]\r
+ [...]\r
+ A scheme-relative URL must be "//", optionally followed by userinfo and "@", followed by a host, optionally followed by ":" and a port, optionally followed by an absolute-path-relative URL.\r
+ [...]\r
+ An absolute-path-relative URL must be "/", followed by a path-relative URL that does not start with "/".\r
\r
https://url.spec.whatwg.org/#writing\r
\r