Closed
Bug 694736
Opened 13 years ago
Closed 13 years ago
Storage server 404s do not comply with Storage API 1.1 spec
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 693860
People
(Reporter: rnewman, Unassigned)
Details
From <http://docs.services.mozilla.com/storage/apis-1.1.html#headers>: X-Weave-Timestamp This header will be sent back with all requests, indicating the current timestamp on the server. If the request was a PUT or POST, this will also be the modification date of any WBOs submitted or modified. and yet: [22:29:13.036] (new Weave.Resource(Service.storageURL + "meta/foobarbaz")).get().headers; [22:29:13.249] ({'content-type':"text/html; charset=UTF-8", 'strict-transport-security':"max-age=86400", date:"Sat, 15 Oct 2011 05:29:13 GMT", connection:"Keep-Alive", 'content-length':"154"}) It seems like a few minutes of reading the Python server source alongside the spec would be a quicker way of finding all of these compliance issues than for me to file them one by one...
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•