[openthread_border_router] Add ingress support
Describe the issue you are experiencing
The OpenThread Border Router AddOn has a status webpage, defaults to port 8080 and an api on port 8081 which is useful to check mesh Topology and such.
Please migrate these to the ingress system built into HA.
Right now, the interface must be accessed over http because the frontend on port 8080 calls port 8081 over http which causes a mixed content error.
Usage of HTTP in browsers is entirely blocked on my domain due to preloaded HSTS.
An additional bug, content is being sent to the user using content-type text/plain, which causes X-Content-Type-Options: nosniff to block it.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
OpenThread Border Router
What is the version of the add-on?
2.13.0
Steps to reproduce the issue
- Try to access
https://ha.example.com/hassio/ingress/core_openthread_border_router- fail because not implemented
- Reverse proxy to the addon using
https://thread-ha.example.com/to backend urlhttps://ha.example.com:8080- website loads fine but the topology page fails due to trying to load resources via
http://ha.example.com:8081
- website loads fine but the topology page fails due to trying to load resources via
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not stale
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not stale
I searched the feature requests and posted there but now found this issue. I agree, this is sorely needed, especially since Thread is by far the most unreliable network I run (compared to Zigbee and Z-Wave). I need to access that page fairly frequently.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not stale
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not stale, wow this bot needs to like 2x its timeout...