The feed Im trying to download is http://feeds.feedburner.com/lrrcast, however I'm getting the "Illegal character in path index"
The feed used to work with out any issue but started throwing this error about a month ago.
The feed Im trying to download is http://feeds.feedburner.com/lrrcast, however I'm getting the "Illegal character in path index"
The feed used to work with out any issue but started throwing this error about a month ago.
Subscribe to the feed from DC's search feeds option (Loading Ready Run - Listed first Audio - Video listed third) press the + icon. On the feeds screen, long press on the warning on the audio version, DC will fix an issue with duplicate filenames.
I deleted the feed and added it again using the method listed, however I'm still getting the same error.
What else could be the issue here ?
I think the feed is supposed to be mp3 or m4a audio files, but the publisher has it listed as type="video/quicktime" should be type="audio/mp3"/> or type="audio/m4a"/>
or it's an enhanced podcast, this is on Eric's to do list http://mantis.snoggdoggler.com/view.php?id=275 & http://mantis.snoggdoggler.com/view.php?id=1539 for support enhanced podcasts (chapter/images/iD3)
For some reason it worked yesterday when I added the feed, but not now, the TapTapConcede episode is the only one that works now. I would contact the publisher & let them know.
paul at loadingreadyrun dot com
Are you using a custom rom? What version of android are you using?
If I understand you correctly, you are unable to add the feed right?
I'm able to add the feed ok, so it's possible that the android code that parses the feed is different on your device and that's causing the problem.
I'm running Cyanogenmod 9 which is android 4.0.4. I can add the feed fine but when it attempts to download the file I receive the illegal character in path at index error.
It looks like they have a character in the filename that is cause us to choke when we write the file to the sd card. I created an issue for this - http://mantis.snoggdoggler.com/view.php?id=1648
Thanks for reporting the problem.
Given that it's Unix, I would expect & to be a perfectly valid filename character.
After checking out the RSS feed in question, I very much suspect this is the same bug that I'm seeing in http://www.doggcatcher.com/node/5904 ... it looks like DoggCatcher is properly decoding the &, %5B, and %5D encodings when reading the media URL out of the RSS feed, but it is failing to convert the &, [, and ] characters (among others?) back into the appropriate encoding when it comes time to generate a java.net.URI so that the file can be downloaded.
I did some digging, and even though the url is encoded, the http library that I'm using is choking on one of the encoded values. I haven't been able to work around this.