NextURL incorrect
Hi there,
when using your facebook-lookup-posts endpoint to extract posts, I noticed that the returning string can have different “formats”, depending on the channel. For TMobile and hugoboss the nexturl doesn’t work:
https://www.facebook.com%2Fpages_reaction_units%2Fmore%2F%3Fprivacy_mutation_token%3DeyJ0eXBlIjowLCJjcmVhdGlvbl90aW1lIjoxNjY2NTU0NTEzLCJjYWxsc2l0ZV9pZCI6NjgzMjQxNzc1NzExMjE3fQ%3D%3D%26page_id%3D108726828894%26cursor%3D%7B%22timeline_cursor%22%3A%22AQHRBVkVm6XQrhwJXXw3bHNSpaS4PNpVh0dbqd-I0spPSQ2F5C-axsviQg4P2zRmiu8lANSXah11Ui5eP-4HX3iEy7txllRPO1xUqfH_6RyA2ciUAhMCM2BybEvKkFBDAVW1%22%2C%22timeline_section_cursor%22%3A%7B%7D%2C%22has_next_page%22%3Atrue%7D%26surface%3Dwww_pages_posts%26unit_count%3D20%26__a%3D1
How come the result changes in the XML Structure depending on the channel and how do I have to format the nextURL string to work for these channels?
Kind regards
Присоединяйтесь к обсуждению – добавьте комментарий ниже:
Hi,
we just tested the URL, and it’s working. Some http libraries tries to encode query parameter, but this URL is already encoded by our application.
Please decode first the URL and then pass it to your http requets. The changes from the structure comes from facebook itself, they currently maintain two different formats. We have a parser for both formats, but to do this it requires two different URLs. Just invoke a decode of the URL for all “nextUrl” you pass as query parameter.
Best Regards
Axesso Support