Closed
Bug 774920
Opened 13 years ago
Closed 13 years ago
Limit number of ids allowed in GET /storage/collection
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Unassigned)
References
Details
(Whiteboard: [qa?])
Attachments
(2 files)
1.35 KB,
patch
|
gps
:
review+
|
Details | Diff | Splinter Review |
2.37 KB,
patch
|
telliott
:
review+
|
Details | Diff | Splinter Review |
DELETE /storage/collection?ids=<blah> is hard-limited to 100 ids. We should do the same for GET.
Updated•13 years ago
|
Whiteboard: [qa-]
Updated•13 years ago
|
Whiteboard: [qa-] → [qa?]
Reporter | ||
Comment 1•13 years ago
|
||
Attachment #651234 -
Flags: review?(gps)
Reporter | ||
Comment 2•13 years ago
|
||
Attachment #651235 -
Flags: review?(telliott)
Reporter | ||
Comment 3•13 years ago
|
||
Just to be clear, this limits the number of ids that can be specified in the "ids" query parameter, not the number that can be returned from the query.
Comment 4•13 years ago
|
||
Comment on attachment 651235 [details] [diff] [review]
code patch limiting max-ids-per-get to 100
That test is a big square of code - might want to put in some spaces before the comments just to break it up a bit. Code is good.
Attachment #651235 -
Flags: review?(telliott) → review+
Comment 5•13 years ago
|
||
Comment on attachment 651234 [details] [diff] [review]
docs patch limiting ids-per-get to 100
Review of attachment 651234 [details] [diff] [review]:
-----------------------------------------------------------------
LGTM
Attachment #651234 -
Flags: review?(gps) → review+
Reporter | ||
Comment 6•13 years ago
|
||
https://github.com/mozilla-services/docs/commit/1fb1ee97f6b7fe6065b79bb2a768c1a89cc488d9
https://github.com/mozilla-services/server-syncstorage/commit/bb44a911c12db4f9f22ac95009beb7b2169a2729
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•