URL Calling character limit

[Byron Poland]

Is there anyway to get around the URL character limit with the URL calling feature?  I need to add a auth token but the token it's self is 184 characters.  thanks.

[Zhiheng Cao]

The character limit only applies to "call from tag manager" option case. If you need auth token most likely the URL is available to be called from external internet. 

On Wed, Mar 6, 2019 at 10:55 AM Byron Poland <wpo...@gmail.com> wrote:

Is there anyway to get around the URL character limit with the URL calling feature?  I need to add a auth token but the token it's self is 184 characters.  thanks.

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.
To post to this group, send email to wireless-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/wireless-sensor-tags.
For more options, visit https://groups.google.com/d/optout.

[Byron Poland]

the call is to my local Home Assistant moving forward un-authenticated calls will stop working.  I enjoyed the local only aspect of the "call from tag manager" feature

[Zhiheng Cao]

Does Home Assistant also support HTTPS?  If so, you could open your firewall to allow incoming HTTPS calls to your Home Assistant with that authentication.  Your external IP address will be the same as your tag manager's IP address so it does not matter if it changes once in a while.  We can introduce a special flag in the URL to make it call externally to your tag manager IP address. 

[Byron Poland]

Yes but local or external Home Assistant will need a authorization bearer token to access the api to post the calls.  It’s just a header in the json but as I mentioned the token itself is over the current character limitation.

They are hardening the security of the platform which is needed.  The other option is to use web sockets but I think that is way beyond my level and also what is already provided through the tag manager and url calling.  When really just need more characters to make it work.

[Byron Poland]

So I got around this by using https://www.npmjs.com/package/json-proxy to proxy and forward the url call and inject the Authorization Bearer token into the header.  

[Zhiheng Cao]

>Yes but local or external Home Assistant will need a authorization bearer token to access the api to post the calls.  It’s just a header in the json but as I mentioned the token itself is over the current character limitation.

If the call is made externally rather than from the Tag Manager, anything (adding header, etc) can be added. The character limit and no ability to define custom HTTP header just applies to calls made from Tag Manager. It is related to the hardware limitation of the tag manager.  

[Byron Poland]

Got it. and understood now, like the calls coming in locally vs is relying on cloud. hopefully this thread can help others if needed.