Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/:channel/content/:node (posts) not respecting parameters (max/after) #110

Open
scholary-tim opened this issue Jun 6, 2013 · 1 comment
Labels
Milestone

Comments

@scholary-tim
Copy link

Re: https://buddycloud.org/wiki/buddycloud_HTTP_API#.2F:channel.2Fcontent.2F:node

If I try to GET: http://api.buddycloud.org/tjdurden2@buddycloud.org/content/posts?asdfsdf=adsfsadf - I would expect it to fail (possibly 400 response?), as the param is not recognised/erroneous.

According to the wiki, only the 'max' and 'after' params should be allowed for this request.

At present, neither the max/after params are respected, nor is there validation to ensure the correct params are passed.

@scholary-tim
Copy link
Author

When testing with JSON, I'm finding that:

max=abc returns ALL results.
max=0 returns ALL results.
max=1 returns 0 results.
max=2 returns 1 result.
max=3 returns 2 results.

However, when adding the 'after' param (e.g. &after=3961d63f-295f-4c75-9993-b26afc67db46), the value of max is seemingly correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant