Minimizing of the configuration sample (#1041)

source/_components/http.markdown

@@ -21,15 +21,6 @@ It's HIGHLY recommended that you set the `api_password`, especially if you are p
 # Example configuration.yaml entry
 http:
   api_password: YOUR_PASSWORD
-  server_port: 12345
-  ssl_certificate: /etc/letsencrypt/live/hass.example.com/fullchain.pem
-  ssl_key: /etc/letsencrypt/live/hass.example.com/privkey.pem
-  cors_allowed_origins:
-    - https://google.com
-    - https://home-assistant.io
-  approved_ips:
-    - 127.0.0.1
-    - 192.168.1.9
 ```
 
 Configuration variables:
@@ -43,6 +34,22 @@ Configuration variables:
 - **cors_allowed_origins** (*Optional*): A list of origin domain names to allow [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) requests from. Enabling this will set the `Access-Control-Allow-Origin` header to the Origin header if it is found in the list, and the `Access-Control-Allow-Headers` header to `Origin, Accept, X-Requested-With, Content-type, X-HA-access`. You must provide the exact Origin, i.e. `https://home-assistant.io` will allow requests from `https://home-assistant.io` but __not__ `http://home-assistant.io`.
 - **approved_ips** (*Optional*): A list of approved ips. Then it will be possible to login from given ips without providing a password.
 
+The sample below shows a configuration entry with possible values: 
+
+```yaml
+# Example configuration.yaml entry
+http:
+  api_password: YOUR_PASSWORD
+  server_port: 12345
+  ssl_certificate: /etc/letsencrypt/live/hass.example.com/fullchain.pem
+  ssl_key: /etc/letsencrypt/live/hass.example.com/privkey.pem
+  cors_allowed_origins:
+    - https://google.com
+    - https://home-assistant.io
+  approved_ips:
+    - 127.0.0.1
+    - 192.168.1.9
+```
 
 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/).