Closed Bug 1001442 Opened 11 years ago Closed 11 years ago

[tarako] Use CDN to cache API collection endpoint

Categories

(Marketplace Graveyard :: Consumer Pages, defect, P1)

Product:
Marketplace Graveyard
Component:
Consumer Pages
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2014-04-29

People

(Reporter: mat, Assigned: mat)

References

Details

(Whiteboard: [qa-])

In fireplace and yogafire we need to use the CDN to cache /api/v1/fireplace/collection/<slug>/. Even more important in yogafire as it's using that for its homepage. Per discussion in https://github.com/mozilla/yogafire/commit/8df7d2dd57da53f45eb099c421c9d9327a5e77c3#commitcomment-6123128 we also need to create 'tarako-featured' collection on dev and stage, and populate it like it is on prod.
Assignee: nobody → clouserw
The only URL this affects is: /api/v1/fireplace/collection/tarako-featured/ Categories use search/featured which is already behind the CDN.
Assignee: clouserw → nobody
Assignee: nobody → clouserw
Alright, "tarako-featured" collections exist on dev/stage/prod now. Jason added the CDN endpoint. https://marketplace-dev.mozflare.net/api/v1/fireplace/collection/tarako-featured/?x -> mathieu for adjusting the code
Assignee: clouserw → mpillard
Target Milestone: --- → 2014-04-29
Fixed in https://github.com/mozilla/yogafire/commit/ac01fa5d6785eb496d2bf3056ec850e70959381d
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Please add STR here or mark it with [qa-] if no QA is needed.
Flags: needinfo?(mpillard)
Flags: needinfo?(mpillard)
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.