For one reason or another , they split the request into secondary part. Possibly to avoid web crawlers.
Anyway, some aditional post request is needed before sending back a "raw" body response
via : /api/searchTVShow/:showID
its some post @ http://thewatchseries.to/show/load-more-links
with x-www-form-urlencoded data resembling something like this. However, i'm not sure still where the season object comes from, or who in the hell ever calls loadMoreLinks(season)
Then we need to execute a jquery command , well actually multiple javascript execs and jquery execs on the 2nd returned response. And then finally send back an "updated" , "raw" body response. And the client side parser "should" theoretically parse it as normal.
Basically its just updating the "unkown" , "placeholder" episode names
For one reason or another , they split the request into secondary part. Possibly to avoid web crawlers.
Anyway, some aditional post request is needed before sending back a "raw" body response via : /api/searchTVShow/:showID its some post @ http://thewatchseries.to/show/load-more-links with x-www-form-urlencoded data resembling something like this. However, i'm not sure still where the season object comes from, or who in the hell ever calls loadMoreLinks(season)
{ 'show_id' : 7651, 'season' : season, 'order' : 'orderDescendingBoth' },
Then we need to execute a jquery command , well actually multiple javascript execs and jquery execs on the 2nd returned response. And then finally send back an "updated" , "raw" body response. And the client side parser "should" theoretically parse it as normal.
Basically its just updating the "unkown" , "placeholder" episode names