Atom feeds with specific URLs not working - first path segment in URL cannot contain colon
Checklist
- [X] I have used the search function for OPEN issues to see if someone else has already submitted the same bug report.
- [X] I have also used the search function for CLOSED issues to see if the problem is already solved and just waiting to be released.
- [X] I will describe the problem with as much detail as possible.
- [X] If the bug only to occurs with a certain feed, I will include the URL of that feed.
App version
2.7.4
Where did you get the app from
F-Droid
Android version
Android 15, GrapheneOS
Device model
Google Pixel 7
First occurred
Just started using it today
Steps to reproduce
Try to add the following ATOM URL as new feed: https://e926.net/posts.atom?tags=+mickey_mouse
Expected behaviour
I assumed the feed could be added like other feeds from that site can be used. A very similar one is working without problem.
Current behaviour
Once you try adding the example link you get the following error:
The cause seems to be the content of the ATOM file, not the URL itself. A very similar link with different results from the page works without problem right now:
https://e926.net/posts.atom?tags=+minnie_mouse
So the error seems to stem especially from one of the image URL sources contained in the ATOM file.
I would've blamed this on the specific website handling the files incorrectly, but for example another Reader, "Capy Reader" for Android on F-Droid can handle the link/file without any problem.
I will attach the ATOM files in their state as of now just in case, as the result of that specific website, which is an image host, might quickly change state.
The problem is not only caused by Pixiv links, like in the current example, but it also happened with some Discordcdn URLs in the ATOM file.
These are .atom files, but I had to rename them to .txt so I could upload them here:
Logs
No response
Nothing to do. The XML is not valid and so can't be parsed.
The error message is misleading. The reason is the initial - in the url: -https://...
This is an error from the site and they should fix their feed.