The REST database does not respect the page parameter

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Reproduce the two requests to /notices/v1/red with page=3 and page=4 and compare their responses, including the reported page value. Then locate the endpoint implementation and pagination handling; done means the requested page is respected and the response reports the corresponding page.

Written by the indexing model from the issue text.

Description

There is an issue with the REST database itself.

There is no difference in the result of 2 requests with different page parameter.

e.g.
Request
https://ws-public.interpol.int/notices/v1/red?**page=4**&resultPerPage=160

return the same response as request
https://ws-public.interpol.int/notices/v1/red?**page=3**&resultPerPage=160

The JSON response does show the page parameter of the request with the value 1.

So it looks like the REST API prefers a default of 1 instead of respecting the parameter of the request.

Dominant language
Python
Stars
16
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bundesAPI/interpol-api

All issues in bundesAPI/interpol-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.