API: Improve Google Reader API level 2 compatibility

[Alkarex]

More specific follow up of #13 and #328

FreshRSS already supports quite well News+ (https://github.com/noinnion/newsplus ).

It was also tested against a modified version of https://github.com/ericmann/gReader-Library

It is currently being tested (alpha beta quality) against a fork of EasyRSS (https://play.google.com/store/apps/details?id=com.pursuer.reader.easyrss).

To improve compatibility, it would be nice to check with additional clients.

See how to get started with the API

[Alkarex]

Support of EasyRSS now at beta quality.

[Jucgshu]

Ok I tried so set up EasyRSS without success. I keep having a "Login failed, please check your username and password" error.

I tried to use a password with or without spaces, numbers or capital letters.

Note that my username starts with a capital letter.

Don't know exactly where to look to be more precise on this one.

Am I missing something ?

• FreshRSS dev branch
• Nginx
• https
• Android 4.1.2

[Alkarex]

How to test the API in the /dev branch:

1. Enable the API access in the FreshRSS configuration page.
2. In the FreshRSS configuration page, define an API password for your user.
3. Browse to http://your.server.example/FreshRSS/p/api/
4. Click on first link to check full configuration:
   • If you see "PASS" then you are done, all is good. You may proceed to step 6.
   • If you see "Bad Request!" or "Not Found", then your server probably does not accept slashes / that are escaped %2F. Proceed to step 5.
   • If you see any other error message, proceed to step 5.
5. Click on the second link to check partial configuration:
   • If you see "PASS", then the problem is indeed that your server does not accept slashes / that are escaped %2F.
     • Under Apache, check http://httpd.apache.org/docs/trunk/mod/core.html#allowencodedslashes
     • Or use a client that does not escape slashes (such as EasyRSS), in which case proceed to step 6
   • If you see "Bad Request!", check your PATH_INFO configuration
     • For nginx, see http://wiki.nginx.org/PHPFcgiExample , Documentation API Google Reader (nginx) #957 (comment)
   • If you see "File not found!" and use nginx, check your fastcgi_split_path_info http://wiki.nginx.org/PHPFcgiExample
   • If you see "Service Unavailable!", then check from step 1 again.
   • If you see "FAIL getallheaders!", the combination of your PHP version and your Web server does not provide access to http://php.net/getallheaders
     • Update to PHP 5.4+ and/or in the case of Apache, use PHP as module instead of CGI, or turn on Apache mod_rewrite.
   • If you see "FAIL 64-bit or GMP extension!", then your PHP version does not pass the requirement of being 64-bit and/or have the http://php.net/gmp extension.
     • The easiest is to add the GMP extension. We may provide other alternatives in the future.
   • Update and try again from step 3.
6. You can now try from a mobile app, using http://your.server.example/FreshRSS/p/api/greader.php as the address, together with your FreshRSS username, and the special API password.

[Alkarex]

@Jucgshu Thanks for testing :-)
I have not checked with nginx yet, but I will make it work.
Please use the procedure just above.
Please check also ./data/log/api.log and/or send it to me.
P.S. Please update FreshRSS to the latest /dev version

[marienfressinaud]

I had the same problem as @Jucgshu with HTTPS. No problem by using HTTP…
Same problem with News+ and I think the problem is the self-signed certificate

[Alkarex]

Self-signed HTTPS certificates may work, but only if you install them on the client obviously.
Did you have good success in HTTP @marienfressinaud then?

In News+, I am aware of one bug, which I think is a bug in News+: when all articles are marked as read on the server, then the synchronisation does not mark them as read in News+. If there is at least one article not read on the server, then the synchronisation is fine.

[marienfressinaud]

Yes, all is fine in HTTP 👍 At least for the moment ;)

[Jucgshu]

Working with a self signed certificate indeed.

Anyway, with or without https, I can't get step 4 to work.

I'm getting "404 Not Found".

(php 5.5)

[Alkarex]

@Jucgshu Is http://your.server.example/FreshRSS/p/api/greader.php found? It should say "Bad Request!".
@marienfressinaud : Did you try with nginx?

[ghost]

As far as getallheaders is concerned, would it be possible to use one of the approaches described here to resolve the issue?

https://secure.php.net/getallheaders

[Alkarex]

@squarefractal Which issue / problem are you talking about?

[ghost]

@Alkarex:
The Google reader API fails to work on configurations using php-fpm due to the absence of getallheaders(), so, would it be possible to add one of the implementations discussed in the comments section of this page to work around this issue?

[Alkarex]

@squarefractal Ok. Could you please create a new dedicated issue for that?

[ghost]

Opened #1127 as per @Alkarex's request

[Alkarex]

Completed with:

• API support for FeedReader #1252
• API: Add management of feeds and categories #1254
• API edit feeds and categories #1261