You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Basic Discovery Service should return a cursor that is useful for the subsequent request. If I do a GET-Request on the following URL: /lookup/shells?limit=2
Seems as curl and postman are quiet fault-tolerant. But at least when I have an id like this 'this&is=a&test' or spaces in the id, we will have a problem.
The Basic Discovery Service should return a cursor that is useful for the subsequent request. If I do a GET-Request on the following URL:
/lookup/shells?limit=2
I get this response for my test:
Also for other services, the id of the last item of the result list is returned, but it is always base64-url-encoded.
I can't use this cursor for the next request:
To Reproduce
Expected behavior
I would like to have a cursor that I can reuse for the next request. The shell id should be base64-url-encoded.
BaSyx (please complete the following information):
System (please complete the following information):
The text was updated successfully, but these errors were encountered: