Version Information
v1.0.0-rainbow2
Hashcat
No response
Description
The new API documentation has wrong pagination documentation / usage:
A call to /api/v2/ui/tasks?page[size]=1 returns (among other data):
"links": {
"self": "<redacted>/api/v2/ui/tasks?page[size]=1",
"first": "<redacted>/api/v2/ui/tasks?page[size]=1",
"last": "<redacted>/api/v2/ui/tasks?page[size]=1&page[before]=eyJwcmltYXJ5Ijp7InRhc2tJZCI6MTA3NX19",
"next": "<redacted>/api/v2/ui/tasks?page[size]=1&page[after]=eyJwcmltYXJ5Ijp7InRhc2tJZCI6MTA3Mn19",
"prev": null
},
The fields page[before] and page[after] are used as base64 encoded strings of a JSON (e.g. {"primary":{"taskId":1075}} )
However, the API documentation shows, that the fields are integer($int32).
Version Information
v1.0.0-rainbow2
Hashcat
No response
Description
The new API documentation has wrong pagination documentation / usage:
A call to
/api/v2/ui/tasks?page[size]=1returns (among other data):The fields
page[before]andpage[after]are used as base64 encoded strings of a JSON (e.g.{"primary":{"taskId":1075}})However, the API documentation shows, that the fields are
integer($int32).