From e1697c11616dabb1850263a2f93fbc685678a39e Mon Sep 17 00:00:00 2001 From: John Date: Mon, 18 Sep 2017 17:27:20 +1200 Subject: [PATCH] Update http.markdown (#3397) * Update http.markdown added self signed cert option and link * Change link --- source/_components/http.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_components/http.markdown b/source/_components/http.markdown index be058d6a342..749c9fa0e15 100644 --- a/source/_components/http.markdown +++ b/source/_components/http.markdown @@ -62,6 +62,8 @@ http: The [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post gives you details about the encryption of your traffic using free certificates from [Let's Encrypt](https://letsencrypt.org/). +Or use a self signed certificate following the instructions here [Self-signed certificate for SSL/TLS](/docs/ecosystem/certificates/tls_self_signed_certificate/) + On top of the `http` component is a [REST API](/developers/rest_api/) and a [Python API](/developers/python_api/) available. There is also support for [Server-sent events](/developers/server_sent_events/). The `http` platforms are not real platforms within the meaning of the terminology used around Home Assistant. Home Assistant's [REST API](/developers/rest_api/) sends and receives messages over HTTP.