use MultiTLS to support separate TLS configs when virtualhosting gemini

fixes #10

1 files changed, 4 insertions, 4 deletions

diff --git a/README.gmi b/README.gmi
index d4bfc34..2a2de46 100644
--- a/README.gmi
+++ b/README.gmi
@@ -423,7 +423,7 @@ Gopher templates also have three additional functions defined:
 
 ## Gemini Templates
 
-The gemini git router defines these routes:
+The gemini and spartan git routers define these routes:
 * / - gemtext listing of the repos in the directory, rendered by repo_root.gmi
 * /:repository/ - gemtext overview of the repository, rendered by repo_home.gmi
 * /:repository/branches - gemtext list of branches/heads, rendered by branch_list.gmi
@@ -520,13 +520,13 @@ gemini {
 	# "code.mydomain.com" does the git hosting defined here
 	host code.mydomain.com
 
+	servertls key /etc/ssl/code.mydomain.pem cert /etc/ssl/code.mydomain.pem
+
 	git /var/repos at /
 }
 ```
 
-Currently a gemini server on a single IP:port can only use a single set of server TLS credentials, so the "servertls" directive is only required on one of the servers and will be used for all of them. That's why the second "gemini" server in the example above has no "servertls" directive. This is the only situation in which servertls is not required in a gemini server (it's already provided in another one with the same IP:port).
-
-=> https://tildegit.org/tjp/sr-71/issues/10 sr-71 issue to use SNI to enable separate TLS certs by domain
+TLS negotiation is done before the request is sent, but sr-71 can use SNI to select the correct certificate to use. So separate gemini servers, even when listening on the same IP and port, can have separate "servertls" directives.
 
 # Extended Gophermap Parsing