Page 1 of 1

Header value being truncated when using <data>

Posted: Tue Aug 28, 2018 11:06 am
by srmoser430
Hi Support Team,

I need your help re: the following code segment:

<log>
<value expr="header_str"/>
</log>

<data name="resp_nearest" src="{{appURL('api/v1/schedule')}}" accept="application/json" method="raw"
enctype="application/json"
headersexpr="header_str" rawexpr="getNearestVisitString(orgid, caregiver.cid)"/>


Here's the issue I'm experiencing:
  • - I log the value of header_str and can see that it is set correctly (it happens to be an "Authorization: Bearer <token>" header with token that is 340 characters in length) immediately before its use in the <data> tag.
    - When I call my URL using the <data> tag, the request gets to my server correctly with the "Authorization: Bearer <token>" header included. However, the token has been truncated to 105 characters so my request fails authentication.
Can you think of a reason why the token value gets truncated when using the <data> tag?

Thanks,
Scott Moser

Re: Header value being truncated when using <data>

Posted: Wed Aug 29, 2018 9:21 am
by support
Hi Scott,

Thank you for bringing this to our attention. Our engineers are looking into it, and we will let you know when there is an update.

Regards,
Plum Support

Re: Header value being truncated when using <data>

Posted: Wed Aug 29, 2018 3:56 pm
by srmoser430
Thanks...

Can you give me an ETA on when I can expect a response? My development is stalled until I can support authentication to my API.

Re: Header value being truncated when using <data>

Posted: Thu Sep 06, 2018 9:01 am
by support
Hi Scott,

We expect to have a patch deployed for this issue by EOB today. We will let you know when it is deployed.

Regards,
Plum Support

Re: Header value being truncated when using <data>

Posted: Fri Sep 07, 2018 8:59 am
by support
Hi Scott,

The patch had now been deployed. Please let us know if you are still experiencing this issue.

Regards,
Plum Support

Re: Header value being truncated when using <data>

Posted: Fri Sep 07, 2018 10:15 am
by srmoser430
I've been testing since earlier this morning and it seems to be working well.

Thanks for your help with this important update!

Scott