Skip to content

Handle non-hal+json responses #134

Open
@espen

Description

@espen

Responses are currently required to be hal+json. The API we consume returns a 201 without data and a http header for a new location when we do a _post. The request is successful but Hyperclient gives a InvalidRepresentationError due to the response not being hal+json.

This works in v0.8.5 but not in the latest version due to 1c7dc4c

I'll provide a failing test later.

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