From 334fc049811d70dbdeeef49f33b5d64a2827b708 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tarjei=20Hus=C3=B8y?= Date: Mon, 6 Jun 2016 10:51:39 -0700 Subject: [PATCH] Change docs link from connect modes to ssl --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d17771e..f583430 100644 --- a/README.md +++ b/README.md @@ -67,4 +67,4 @@ If you only have one database you can add its certificate to your trust store to If you're connecting to a database pool or are hosting many databases you should probably create your own Certificate Authority (CA) that can sign certificates for each database. Then the clients only need to trust the CA certificate and will have a secure connection to any of the databases signed by the CA. -As always, consult the [excellent documentation](https://www.postgresql.org/docs/9.0/static/libpq-connect.html#LIBPQ-CONNECT-SSLMODE) for details. +As always, consult the [excellent documentation](https://www.postgresql.org/docs/9.0/static/libpq-ssl.html) for details.