Allow "http request header - key" with up to 270 characters (Bearer TOKEN)

[falcke]

Hi!
How about allowing "http request header - key" with up to 270 characters for the "http(s) + JSON" power meter configuration?
Why?
Home Assistant allows you to access with a REST API. It works by using a Bearer "Long-Lived Access Token" (docs).
Right now OpenDTU-OnBattery 2024.01.26 allows you to use up to 64 characters for this configuration.
In my case 270 characters would be needed due to the length of the token.
This could be handy if your meter reader is directly connected to your home assistant.

[schlimmchen]

You are supposed to put Authorization as "Optional: HTTP request header - Key" and Bearer <TOKEN> as "Optional: HTTP request header - Value". How long is the ? The value field allows up to 256 chars, so your token can be 256-7=249 chars long. Given that you ask for 270 chars and that the Authorization: Bearer part should be part of those 270 chars, if I guessed your misunderstanding correctly, your token is 270-22=248 chars long, so you should be good to go?!

I just generated such a long lived access token and mine is 183 chars. Why should yours be so much longer? I'm confused.

Note that I am not 100% sure about this. But maybe 85%. The token goes into the value field and that's long enough.

[falcke]

Make your 85% a 100%. I've re-tested it and you were right! 👍

[schlimmchen]

Nice, glad I could help. Please mark this discussion as solved/answered.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.