mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-14 21:06:50 +00:00
Update http.markdown (#38626)
This commit is contained in:
parent
da2810479c
commit
61d69b6f3e
@ -35,7 +35,7 @@ server_host:
|
||||
type: [list, string]
|
||||
default: "0.0.0.0, ::"
|
||||
server_port:
|
||||
description: Let you set a port to use.
|
||||
description: Allows you to specify which port Home Assistant should listen on.
|
||||
required: false
|
||||
type: integer
|
||||
default: 8123
|
||||
@ -75,7 +75,7 @@ ip_ban_enabled:
|
||||
type: boolean
|
||||
default: true
|
||||
login_attempts_threshold:
|
||||
description: "Number of failed login attempt from single IP after which it will be automatically banned if `ip_ban_enabled` is `true`. When set to -1 no new automatic bans will be added."
|
||||
description: "Number of failed login attempts from a single IP after which it will be automatically banned if `ip_ban_enabled` is `true`. When set to -1 no new automatic bans will be added."
|
||||
required: false
|
||||
type: integer
|
||||
default: -1
|
||||
@ -129,7 +129,7 @@ The `http` platforms are not real platforms within the meaning of the terminolog
|
||||
|
||||
To use those kind of [sensors](#sensor) or [binary sensors](#binary-sensor) in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.
|
||||
|
||||
If you want to use HTTP sensors, create a [Long-Lived Access Tokens](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token) in the Home Assistant UI in the **Security** section of your {% my profile title="**User profile**" %} page.
|
||||
If you want to use an HTTP sensor, create a [Long-Lived Access Token](https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token) in the Home Assistant UI in the **Security** section of your {% my profile title="**User profile**" %} page.
|
||||
|
||||
All [requests](https://developers.home-assistant.io/docs/api/rest#post-apistatesentity_id) need to be sent to the endpoint of the device and must be **POST**.
|
||||
|
||||
@ -142,7 +142,14 @@ If you want to apply additional IP filtering, and automatically ban brute force
|
||||
banned_at: "2016-11-16T19:20:03"
|
||||
```
|
||||
|
||||
After a ban is added a Persistent Notification is populated to the Home Assistant frontend.
|
||||
After a ban is added a Persistent Notification will appear in the Home Assistant frontend.
|
||||
|
||||
To clear an IP ban, you can either:
|
||||
|
||||
- Remove the specific IP entry from `ip_bans.yaml`, or
|
||||
- Delete the entire `ip_bans.yaml` file. It will be recreated automatically the next time a ban occurs.
|
||||
|
||||
After making changes, restart Home Assistant to apply them.
|
||||
|
||||
## Hosting files
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user