Skip to content

All Scalar API Client responses aren't able to render claiming a missing Content-Type header #2401

@martinezdylan

Description

@martinezdylan

Bug description

All of our endpoints are failing to render within the Scalar API Client with it claiming a missing header Content-Type is missing. We've confirmed the the right headers are found in the response & it works in Postman as well as CURL. See below:

Screenshot 2024-07-23 at 10 01 31 PM

How to reproduce

  1. Navigate to https://docs.libum.io/nexum/symxchange/api-reference/persistent/informationservice
  2. Click "Test it"
  3. Ping me for an API key & use it as Bearer token
  4. Click "Send"

Additional context

This was working as recently as July 17th, 2024. I'm not sure what changed but need this fixed ASAP if possible.

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