Skip to content
This repository was archived by the owner on Oct 18, 2022. It is now read-only.
This repository was archived by the owner on Oct 18, 2022. It is now read-only.

Error when content-type is incorrect #75

Open
@wgahnagl

Description

@wgahnagl

Hey!
I've hit this error when receiving improperly formatted headers from remote servers. I know this is definitely supposed to work as written, and it is the server's fault for being improperly formatted, but it still makes it impossible to use this library's responses, despite the actual body of the response being valid xml.

Do you think there would be any value in creating a way to deliberately override or skip this function's content-type check?

format!("expected Content-Type 'text/xml', got '{}/{}'", ty, sub).into(),

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions