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

Error when content-type is incorrect #75

Open
wgahnagl opened this issue Oct 29, 2021 · 0 comments
Open

Error when content-type is incorrect #75

wgahnagl opened this issue Oct 29, 2021 · 0 comments

Comments

@wgahnagl
Copy link
Contributor

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(),

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant