RSS: Sourceforge RSS feeds not loading.
Brought to you by:
adamfranco
Sourceforge exports RSS 2.0 feeds, but these aren't working in the feed-display plugin.
Example:
http://sourceforge.net/export/rss2_projnews.php?group_id=82171&rss_fulltext=1
Logged In: YES
user_id=789554
Originator: YES
The issue seems to be that on the production server, the url-encoded question mark is being treated as an actual question mark and the string following it is (improperly) being added to the query string.
Not sure how to fix this. Need to investigate further.
Logged In: YES
user_id=789554
Originator: YES
I've been troubleshooting a Segue 2 issue that occurs with with urls that include encoded question marks.
For example, this URL to load an RSS feed results broken PATH_INFO data:
https://segue2.middlebury.edu/plugin_manager/plugin_action/plugin/SeguePlugins%3A%3Aedu.middlebury%3A%3ARssFeed/paction/remote_feed/url/http%3A_slash__slash_sourceforge.net_slash_export_slash_rss2_projnews.php%3Fgroup_id%3D82171%26rss_fulltext%3D1
while the same url with the index.php in it works fine:
https://segue2.middlebury.edu/index.php/plugin_manager/plugin_action/plugin/SeguePlugins%3A%3Aedu.middlebury%3A%3ARssFeed/paction/remote_feed/url/http%3A_slash__slash_sourceforge.net_slash_export_slash_rss2_projnews.php%3Fgroup_id%3D82171%26rss_fulltext%3D1
I have determined that this issue is with our URL rewriting.
The current rewrite directive is
<Directory "/path/to/segue2/">
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule (.*) /index.php/$1
</IfModule>
</Directory>
I've tried (on termite) adding some of the options such as [NE] and [QSA] to the end of the rule line, but with no success. Thoughts on improvements to this directive that would keep the path info from being truncated at %3F?
I guess if this is not possible with mod_rewrite I could add a special case handler in Segue's configuration to read path-info out of the REQUEST_URI rather than taking what PHP gives me, but I fear that that route would involve a lot of special cases and would be less portable.
Logged In: YES
user_id=789554
Originator: YES
We can't seem to find any way to fix this in Apache 2.2.3. Will do a work-around in Segue/Harmoni.
Logged In: YES
user_id=789554
Originator: YES
In Harmoni:
Request: PathInfoRequest handler now replaces encoded question marks "%3F" with a "_quest_" placeholder to get around an issue with Apache's mod_rewrite accidentally decoding encoded question marks in some situations. This solution works whether or not mod_rewrite is used.