You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.
A sender that generates a message containing a payload body SHOULD generate a Content-Type header field in that message unless the intended media type of the enclosed representation is unknown to the sender. If a Content-Type header field is not present, the recipient MAY either assume a media type of "application/octet-stream" ([RFC2046], Section 4.5.1) or examine the data to determine its type.
It means that the Content-Type HTTP header should be set for PUT and POST requests.
Currently, the
POST
request does not work properly in_do_api_call
as the Content-Type HTTP header should be set for PUT and POST requests.Here by default the content type is not set for
POST
which results in the 415 error like the following:This is done as part of
PATCH
calls as https://github.com/fivetran/airflow-provider-fivetran/blob/main/fivetran_provider/hooks/fivetran.py#L117Similar change is required for
POST
callsReferences:
According to the RFC 7231 section 3.1.5.5:
It means that the Content-Type HTTP header should be set for PUT and POST requests.
Change required:
Add the following line after: https://github.com/fivetran/airflow-provider-fivetran/blob/main/fivetran_provider/hooks/fivetran.py#L114
The text was updated successfully, but these errors were encountered: