Open geso02 opened 2 months ago
I just tried to do the GET request for my example and it works:
curl http://localhost:8091/lookup/shells?cursor=https://acplt.org/Test_AssetAdministrationShell2
=>{"paging_metadata":{},"result":["https://acplt.org/Test_AssetAdministrationShell3"]}
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.
Hi Gerhard, Thanks for reporting this bug. We will look into it. And as always, if you have the time, please feel free to provide the fix yourself.
I will move this bug ticket to ready to be picked up. If you decide to work on it, please let me know.
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):