Addition of Pocket ID to SPOC endpoint requests
Categories
(Firefox :: New Tab Page, task, P1)
Tracking
()
People
(Reporter: thecount, Assigned: thecount)
References
Details
(Keywords: github-merged)
Attachments
(3 files)
With Adzerk, we need to be passing a pocket user id to the spoc request.
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
•
|
||
Chatted with Digi today, to double check something. Looks like we'll need to send the id over with a post and not a get. Currently the spoc request is a get, and it passes consumer_key along as a query param. If we move this over to a post, and include the pocket impression_id as a payload item, I'll also want to send consumer_key over as a payload item too.
The payload changes I'll be sending in the spoc request post are:
{
consumer_key: "abcd",
impression_id: "abcd",
}
Mathijs, does that make sense to you, and is there something separate you need to track for any potential changes needed to be made on the back end?
Comment 4•6 years ago
|
||
I'll make sure the Proxy Server accepts a Post request. I'll let you know when the OpenAPI spec is ready.
Comment 5•6 years ago
|
||
The priority flag is not set for this bug.
:tspurway, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
To test:
- Set
browser.newtabpage.activity-stream.discoverystream.config
to default - In browser console, open up the network tab and probably clear it.
- in about:config, change
browser.newtabpage.activity-stream.discoverystream.config
to{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":true,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}
- In the network tab, you should now see a POST to unique-spocs and also check that requests params tab for something along these lines:
{"pocket_id":"{123-123-123-123-123}","consumer_key":"123345678"}
Assignee | ||
Comment 7•5 years ago
|
||
This got merged.
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Assignee | ||
Comment 9•5 years ago
|
||
Comment 10•5 years ago
|
||
Is this something we need to uplift to Beta or can it ride the trains?
Updated•5 years ago
|
Assignee | ||
Comment 12•5 years ago
|
||
You are correct we don't need this uplifted, 69 is fine.
Description
•