Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strip known bad character sequence before parsing #253

Merged
merged 2 commits into from
Dec 9, 2016

Conversation

gshutler
Copy link
Member

@gshutler gshutler commented Dec 5, 2016

The bad character sequence leads to the whole response failing to parse.

Specifically this is the substitute character and is not valid for
use in XML. Therefore, this change should be safe, or at least lead to a
preferable outcome to outright failure.

Related issues: #166 #219

The bad character sequence leads to the whole response failing to parse.

Specifically this is the [substitute character][1] and is not valid for
use in XML. Therefore, this change should be safe, or at least lead to a
preferable outcome to outright failure.

[1]: https://en.wikipedia.org/wiki/Substitute_character
Removes all the non-printable characters excluded from the XML
[characters specification][1].

[1]: https://www.w3.org/TR/xml/#charsets
@gshutler
Copy link
Member Author

gshutler commented Dec 9, 2016

We've had this live for a few days now and the related errors have disappeared.

@gshutler gshutler merged commit 8d11614 into WinRb:master Dec 9, 2016
@gshutler gshutler deleted the tolerant-parser-vp branch December 9, 2016 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant