Conversation
Example of valid feed not working in SimplePie: https://haveibeenpwned.com/feed/breaches/ Regression due to simplepie#445 The final character `>` of a feed is encoded as `3E00` in UTF-16LE, so calling `trim()` was removing the `\x00`, breaking the multibyte encoding and making the feed invalid. Downstream issue FreshRSS/FreshRSS#7690
Alkarex
added a commit
to Alkarex/FreshRSS
that referenced
this pull request
Jun 24, 2025
Fix FreshRSS#7690 FreshRSS/simplepie#40 The final character `>` of a feed is encoded as `3E00` in UTF-16LE, so calling `trim()` was removing the `\x00`, breaking the multibyte encoding and making the feed invalid. Upstream PR simplepie/simplepie#916
This was referenced Jun 24, 2025
Merged
Alkarex
added a commit
that referenced
this pull request
Jun 25, 2025
simplepie#917 Slight refactor of simplepie#916 (#40) to cover all paths. Missing paths included the fsock method without gzip (e.g. deflate or plain).
Alkarex
added a commit
to Alkarex/FreshRSS
that referenced
this pull request
Jun 25, 2025
FreshRSS/simplepie#42 simplepie/simplepie#917 Slight refactor of simplepie/simplepie#916 (FreshRSS/simplepie#40) to cover all paths. Missing paths included the fsock method without gzip (e.g. deflate or plain).
Alkarex
added a commit
to FreshRSS/FreshRSS
that referenced
this pull request
Jun 25, 2025
* Fix feeds encoded in UTF-16LE Fix #7690 FreshRSS/simplepie#40 The final character `>` of a feed is encoded as `3E00` in UTF-16LE, so calling `trim()` was removing the `\x00`, breaking the multibyte encoding and making the feed invalid. Upstream PR simplepie/simplepie#916 * Trim body for all paths FreshRSS/simplepie#42 simplepie/simplepie#917 Slight refactor of simplepie/simplepie#916 (FreshRSS/simplepie#40) to cover all paths. Missing paths included the fsock method without gzip (e.g. deflate or plain).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Example of valid feed not working in SimplePie: https://haveibeenpwned.com/feed/breaches/
Regression due to simplepie#445
The final character
>of a feed is encoded as3E00in UTF-16LE, so callingtrim()was removing the\x00, breaking the multibyte encoding and making the feed invalid.Downstream issue FreshRSS/FreshRSS#7690
Upstream PR simplepie#916