Markdown copied that too: https://spec.commonmark.org/0.29/#autolink
<http://google.com/search?q=How to bake cakes>
Thank you!
Although it's recommended that you encode them in user representation (for this reason) you can certainly should be able to send a space character through at the protocol level and if not it's a bug.
Note that a space is not valid in the host name portion if you are using DNS (which most URLs do, of course).
> 2.4.3. Excluded US-ASCII Characters
> Although they are disallowed within the URI syntax, we include here a description of those US-ASCII characters that have been excluded and the reasons for their exclusion.
[...]
> space = <US-ASCII coded character 20 hexadecimal>
You can certainly encode spaces in URLs but the URL will not contain spaces.
The regular expression in appendix B is irrelevant because it assumes a well-formed URL so spaces do not need to be explicitly excluded.
And at the protocol level you certainly can't use spaces in URLs (in HTTP 1.1) because the request line uses spaces to delimit the URL or path.
If I write into my smartphone notes a url, I prefer to write something like:
Http://google.com/search?q=How to bake cakes$
Than
Http://google.com/search?q=How+to+bake+cakes
iOS Notes treats the second one as a URL and the first one partially as a URL