Using fiddler to analyze the Android version of the API

Using fiddler to analyze the Android version of the API

The first tool to prepare:

• Android Phone + informed daily app;
• Fiddler (the famous Telerik out, Telerik);
• Lan.

The principle is simple, open fiddler, set it up as a proxy, and then set the Android phone proxy on the same local area network to the computer where Fiddler is located.

All HTTP requests from the Android phone are then proxied (Fiddler's Computer), and fiddler can of course capture all the requested data. ( Note that if you capture too many, filter by the filter on the right side of the Fiddler ).

If you are unfamiliar with fiddler children's shoes can be seen here: http://kb.cnblogs.com/page/130367/

After that, open the daily app in the Android phone and you'll see all the HTTP requests:

For example, be sure to filter using filter (right side of the figure). You can see that the daily application of the various operations can see the corresponding API, probably the following:

• Android app version update check;
• App Launcher image
• Daily Theme List Crawl
• Home Recent Articles
• Home page article (by day)
• Topic page Articles
• Topic page Pagination Article
• Article text
• Article additional information (comments, likes, etc.)
• Get a short comment
• Pagination gets short comments
• Get Long comments
• Paging Get long comments

(The API for login is not analyzed)

Each API is requested by a Get method, and most of the returned data is in JSON format (partly HTML). Are some of the APIs I've compiled:

After the source, we can go down to see. The format returned by each API is as follows (for example, grab a list of topic dailies):

The JSON data returned is well handled, and the type of the Windows.Data.Json namespace can be used to resolve all of them. This is the preparation for getting the API section.

Above.

Part

function has not been finished, first look at a few pictures:

Using fiddler to analyze the Android version of the API