You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2022. It is now read-only.
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?
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?
xml-rpc-rs/src/transport.rs
Line 119 in 2dde662
The text was updated successfully, but these errors were encountered: