Errors when using Dwolla call

1

We are getting lots of unspecified errors in our Sandbox and Prod envs., when calling this ; (halUtil.getResourceId(customerFundingSource.getLocationHeader()); Below image is printed in our logs;

image
image1395×351 99 KB

We think getLocationHeader call is returning null.
Looks as if our call to return customer ids is returning null, when it was working as of yesterday
Any insight into this?

2

Hi @khastie ,

Thank you for bringing this matter to our attention. We understand the importance of ensuring seamless integration with our APIs and apologize for any inconvenience this may have caused.

Upon investigating the reported issue, we discovered that our WAF provider recently upgraded a component of our infrastructure to utilize HTTP/2 instead of HTTP/1. While HTTP/1 permits both upper and lower case headers, HTTP/2 mandates that headers must be lowercase. Consequently, some of Dwolla’s response headers were altered from capital to lowercase, such as ‘Location’ becoming ‘location’.

Upon recognizing the impact of this change and the challenges it presented for some clients, we took immediate action to address the situation. We have reverted the infrastructure to utilize HTTP/1, thereby restoring the previous behavior of our response headers.

Moving forward, it’s essential to note that while we have resolved the immediate issue, we are also planning for future upgrades to transition to HTTP/2 fully. As part of this transition, there may be further changes to response headers. We are encouraging all clients to update their code to accommodate case-insensitive response headers, as this will facilitate a smoother transition when we ultimately migrate to HTTP/2.

Once again, we apologize for any disruption caused and appreciate your patience and understanding as we work to enhance our systems and services. To assure you, we do provide prior notification about any intentional API changes made by Dwolla. If you have any further questions or concerns, please don’t hesitate to reach out to our support team.

Best regards,
Shreya

3

Thank you, Shreya. Going forward, when will we know when Dwolla is going to implement changes of this nature before they occur? Are there plans for attempting this again in the future?

4

Hi @khastie, for potentially breaking or disruptive changes like this, we aim to send notifications well in advance to give a chance to all our clients to make necessary changes to avoid disruptions with the integration.

5

This topic was automatically closed after 365 days. New replies are no longer allowed.