First of all, thank you for building this app, it looks and works really well!
I would like to propose a new feature: the ability to configure custom HTTP headers to be sent with API requests, similar to how the BasicAuth header is currently handled.
Use Case / Motivation:
This feature would allow users to secure their TeslaMateAPI instances by placing them behind reverse proxies, zero-trust networks, or edge authentication providers (such as Cloudflare Access, Pomerium, or Pangolin) by passing the necessary authentication tokens.
Currently, the only built-in method for request headers is Basic Authentication. While this works for simple setups, expanding support to arbitrary custom headers provides much greater flexibility for various self-hosted network architectures.
Thank you for your time and for continuing to maintain this project!
First of all, thank you for building this app, it looks and works really well!
I would like to propose a new feature: the ability to configure custom HTTP headers to be sent with API requests, similar to how the BasicAuth header is currently handled.
Use Case / Motivation:
This feature would allow users to secure their TeslaMateAPI instances by placing them behind reverse proxies, zero-trust networks, or edge authentication providers (such as Cloudflare Access, Pomerium, or Pangolin) by passing the necessary authentication tokens.
Currently, the only built-in method for request headers is Basic Authentication. While this works for simple setups, expanding support to arbitrary custom headers provides much greater flexibility for various self-hosted network architectures.
Thank you for your time and for continuing to maintain this project!