Skip to content
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.

Upgrade supported mollie client #12

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

whyscream
Copy link

@whyscream whyscream commented Jan 24, 2023

Upgrade the used Mollie API client to the latest version

We ran into an issue for a legacy project that uses this integration. The v1.x.x client will no longer perform correct GET queries to the API, because of an ugly bug. This has been fixed in newer versions of the client.

Furthermore, the v1.x.x client uses the v1 API at Mollie, which is deprecated and might be disabled after July this year

Tom Hendrikx and others added 2 commits January 23, 2023 18:11
- Uses newest mollie-api-python client
- Uses v2 Mollie API, so no pressure to migrate to the new API

The issue that triggered this change was that the old 1.3.2 client produced a
header that the Mollie API doesn't accept anymore.

For GET requests, an empty JSON body was generated (see https://github.com/mollie/mollie-api-python/blob/2e45f258fadcd3863292b89d709d41f627f7d3ff/Mollie/API/Client.py#L74),
and this triggered requests (or urllib3) to produce a `Content-length: 2` header.
This is incorrect since a GET request has no body, and the Mollie API
apparently checks this since some time.

Rather than fixing the bug in a hard way, just upgrade.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant