Skip to content

TSP Client fails on Content-Type: application/json; charset=utf-8 #155

@JonatanAntoni

Description

@JonatanAntoni

Bug Description:

The current implementation of TSP Client (REST Client) does not accept server replies using Content-Type: application/json; charset=utf-8 as per RFC9110 8.3.2 Charset.

The problem is the strict-equal in

if (response.headers?.get('Content-Type') === 'application/json') {

Steps to Reproduce:

  1. Connect to a TSP Server that replies with Content-Type: application/json; charset=utf-8
  2. See reply to initial GET /tsp/api/health to be dismissed due to Content-Type
  3. No further requests are being issued

Additional Information

  • Operating System: MacOS 26

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions