Skip to content

handle unexpected Content Type some providers may respond with #14

@elf-pavlik

Description

@elf-pavlik

While we focus for now on using PLP Provider, which responds with proper application/ld+json Content Type, we can always expect it. When people publish their profiles elsewhere they can get served with all kind of Content Types, we need to stay liberal here and still parse everything as JSON-LD.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions