Mathieu Leplatre

Results 244 issues of Mathieu Leplatre

``` ➜ http GET https://kinto.dev.mozaws.net/v1/ -a toto:tata | jq .user.bucket "2f5fa495-3fac-913c-bef6-40eacb7c2880" ``` ``` ➜ http GET https://kinto.dev.mozaws.net/v1/buckets/2f5fa495-3fac-913c-bef6-40eacb7c2880 -a toto:tata HTTP/1.1 403 Forbidden Access-Control-Expose-Headers: Cache-Control, Retry-After, Backoff, Last-Modified, Expires, Content-Length, Alert,...

bug
stale

- `write:attributes` (or should it be `write:data` for consistency with payload naming?) - `write:permissions` - `write:{plural}` (eg. `write:records` for collections, or `write:groups` for buckets) - `write` ( =`write:attributes` + `write:permissions`...

enhancement
scope: permissions
stale

I am tempted to believe that we sometimes return a 403 where a 401 would be more appropriate. For example, when an `Authorization` header is sent and no authentication method...

enhancement
question
stale

> This is a follow-up bug of #942 On batch requests, an event is sent for each (parent id / resource / action), and the list of objects is provided...

enhancement
question
stale

For better consistency, permissions principals specified via settings could be presented in the response JSON along others. Related #350

enhancement
protocol
scope: permissions
stale

https://github.com/Kinto/kinto/blob/7ca4ab400504f94966ede6b0f587313f84893f5b/kinto/core/resource/model.py#L278-L282 If the `history` is enabled this user could still see them anyway... OH, and BTW this doesn't seem to be explicited in the docs.

question
scope: permissions
stale

In the accounts API, the setup of administrators requires two steps: * creating the actual accounts * adding the principals in the settings Instead we could have a `kinto createadmin`...

enhancement
scope:authentication
stale

In the docs, we can read: > «If [the specified timestamp] is in the past, the record is created with the timestamp in the past but the list timestamp is...

question
scope: core
documentation
protocol
stale

What happens in the `bump_timestamp()` trigger is hard to monitor and trace (e.g. does not appear on `pg_activity`). We could investigate and see if we could move the behavior elegantly...

enhancement
question
stale

Our use case is the following: for `kinto-http.js` we want an integration test to reproduce the situation where the history plugin was enabled after the creation of the collection. Since...

enhancement
question
stale