Package URIs can't be cached reliably

Bug #1297883 reported by Michael Nelson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Center Agent
Fix Released
Undecided
Natalia Bidart

Bug Description

Currently the uri:

/api/v1/package/click-package-name

is used to GET or DELETE a package, but

/api/v1/update is used to create and update packages.

This gives upstream caches no chance to invalidate uris for packages when they are updated.

We should do something standard like:
PUT /api/v1/package/click-package-name to create or update (or POST /api/v1/package , but we don't really seem to use that as a collection resource)
GET /api/v1/package/click-package-name
DELETE /api/v1/package/click-package-name

We'll need to update sca to use those instead and then remove the update resource.

Tags: caching
tags: added: caching
summary: - Package URIs can't be reliably cached
+ Package URIs can't be cached reliably
James Tait (jamestait)
Changed in click-package-index:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Natalia Bidart (nataliabidart)
Changed in click-package-index:
status: In Progress → Fix Committed
Changed in software-center-agent:
status: New → In Progress
assignee: nobody → Natalia Bidart (nataliabidart)
James Tait (jamestait)
Changed in click-package-index:
status: Fix Committed → Fix Released
assignee: Natalia Bidart (nataliabidart) → nobody
Changed in software-center-agent:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.