Skip to content

Custom headers don't override the default ones #141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
panovitch opened this issue Jul 14, 2021 · 2 comments · May be fixed by #142
Closed
2 tasks done

Custom headers don't override the default ones #141

panovitch opened this issue Jul 14, 2021 · 2 comments · May be fixed by #142

Comments

@panovitch
Copy link

panovitch commented Jul 14, 2021

Steps to reproduce:

  1. Pass a custom header to override the default one, e.g. client-request-id:
Payment.create(
    new Amount("123", "EUR"),
    new Pointer("IBAN", "mockiban"),
    "description",
    123,
    null,
    null,
    false,
    Map(
      BunqHeader.CLIENT_REQUEST_ID.toString -> "123"
    ).toJava)

What should happen:

  1. The specified request header gets passed to the server, and the server recognises the Client Request ID.

What happens:

  1. The server doesnt recognise the passed client request ID, and doesnt deduplicate the requests. Upon further investigation, I found out that the new header value gets appended to the header key, instead of replacing it.

Traceback

SDK version and environment

  • Tested on 1.14.1
  • Sandbox
  • Production

Response id

  • Response id:

Extra info:

panovitch pushed a commit to panovitch/sdk_java that referenced this issue Jul 14, 2021
meslubi2021 added a commit to Unity-Banking-and-financial-institution/sdk_java that referenced this issue Jan 4, 2025
Custom headers now override the default ones (bunq#141)
@two-trick-pony-NL
Copy link
Member

👋 Hey @panovitch

I work at bunq and am currently reviewing the bunq API docs, open issues and SDK’s and came across your issue. I know it’s been open for a while, and I’d love to understand how it’s impacting you. Beyond the obvious -fixing this issue-, what else could we do to improve your experience with our API?

If you want to share your thoughts on how we can improve on our public API:

📅 I'd love to schedule a 15 minute interview to understand your needs through: Calendly
💬 Or if you don't have time for a call, you can give us some general feedback through this form

Your feedback will go straight to our product team! 🚀

@two-trick-pony-NL
Copy link
Member

Hi! We're closing this issue as it's tied to an older version of our SDKs, and we've since completely revamped them as part of bunq Update 28.

This is a fresh start—we've tested the new SDKs extensively, and we’ll be putting them to the test again during our upcoming hackathon this Friday, where we’ll fix idiosyncrasies on the spot. (You’re welcome to join us!)

If this issue (or a new one) shows up with the updated SDKs, feel free to reopen or file a new report—we're happy to jump on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants