Up until now I used a "poor man" approach: the uri parser is barely a parser, it tries to extract the path from the request, with some minor checking, and that's all. This obviously is not RFC3986-compliant. The new RFC3986 (URI) parser should be fully compliant. It may accept some invalid URI, but shouldn't reject or mis-parse valid URI. (in particular, the rule for the path is way more relaxed in this parser than it is in the RFC text). A difference with RFC3986 is that we don't even try to parse the (optional) userinfo part of a URI: following the Gemini spec we treat it as an error. A further caveats is that %2F in the path part of the URI is indistinguishable from a literal '/': this is NOT conforming, but due to the scope and use of gmid, I don't see how treat a %2F sequence in the path (reject the URI?).

"concurrently" means at the same time, which can be confusing when we say that it's single-threaded on a single process.

before the -d option only accepted absolute paths, and this wasn't documented. Even more, with the default value of "docs" it won't work. Now it transforms all relative paths to absolute paths before going on.

The -l option was removed: now it logs on syslog if -f (foreground) is not passed.

internally, gmid doesn’t care if the client issued a certificate, but now we pass that information to the CGI script in some new environment variables.

gemini://example.com was incorrectly parsed.