79ede44ea1
Added new example for two user supplied HTTP headers, subject to checking by the author of the issue. (Missed off the previous commit this this file.)
2.4 KiB
Home | Switches | Actions | Templates | Numeric | Glance | Background Service | Wi-Fi | HTTP Headers | Trouble Shooting | Version History
User Specified Custom HTTP Headers
Principally for those who use HomeAssistant add-on Cloudflared in order to provide additional security via Cloudflare's Web Application Firewall (WAF). But Garmin does not support certificates in requests. And the solution is generic enough for other use cases.
Please let us know if this solution is found to be useful for other situations.
Setup
The settings contain two options for users to specify both the HTTP header name and the value as two free form strings.
If you don't know why you need these, leave them empty and ignore.
Cloudflare WAF rule example
(any(http.request.headers["your-header-name"][*] eq "your-header-key"))
Make the key strong enough!
Cloudflare WAF IP Access example
In order to safely allow API access, both a cf-access-client-id and cf-access-client-secret HTTP headers must be present. Essentially a username and password pair. Please note that the settings do not attempt to hide your password value with '*' characters, it should be private enough on your personal phone Connect IQ app.
Support
None!
The authors of the Garmin HomeAssistant application do not use, and hence do not know, the Cloudflared add-on. While we have enabled the HTTP headers to support using this add-on, it does mean you support yourself. Please do not raise issues about this functionality unless you are supplying the answers for any required changes too!
Credits
With thanks to Lars Pöpperl (@tispokes) for contributing to this solution.