Closed
Bug 845967
Opened 12 years ago
Closed 11 years ago
Etag support
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: andy+bugzilla, Unassigned)
References
Details
(Whiteboard: p=3)
We should consider adding etag support in solitude. This isn't just a matter of sending an etag for caching, but enforcing If-match and if-none-match support so that we can ensure consistency when multiple clients try to update solitude at the same time.
Reporter | ||
Updated•12 years ago
|
Priority: -- → P4
Whiteboard: p=3
Reporter | ||
Comment 1•12 years ago
|
||
The scope of this can pretty large, but this is to re-use the etags added in bug 895172. To ensure that every response
- has an etag for the object
- an etag for the overall response in the HTTP header
Then on PUT and PATCH we require and compare that etag and raise 419. Requiring the etag should be optional, so we can change all the clients to use it.
Assignee: nobody → david
Updated•12 years ago
|
Version: 1.2 → 1.3
Reporter | ||
Updated•12 years ago
|
Version: 1.3 → 1.5
Updated•11 years ago
|
Assignee: david → nobody
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•