Skip to content

bug: HTTP request fail due to no content type header set #908

@joshua-mo-143

Description

@joshua-mo-143
  • I have looked for existing issues (including closed) about this

Bug Report

Direct follow up to #875.

Some of the API calls fail due to no content header set so it tries to parse as... well, something else other than JSON.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions