client should make multiple requests when >500 hash prefixes are queried
Open
- Dominant language
- Go
- Stars
- 503
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
The Safe Browsing API has a limit of 500 hash-prefixes per request (see [update api](https://developers.google.com/safe-browsing/v4/update-api)). The server returns an error when that limit is exceeded (#87).
This client should batch the requests and reassemble.
Contributor guide
Assessment
This issue has not been assessed yet.