-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Store REST API returns invalid digest #2615
Comments
Very good morning @kaichaosun ! The following page is super handy to know how to properly deal with REST service ( kudos to @NagyZoltanPeter ! ) https://waku-org.github.io/waku-rest-api/#get-/store/v1/messages From there, you will see that all the Let me know if that helps and we can close that one :) |
@Ivansete-status It seems the returned base64 encoded digest is not browser friendly, wondering how to fix such a broken link? |
Hey @kaichaosun ! |
It's returned in json of first request, https://github.com/threeproto/ferry-chat/blob/main/src/App.tsx#L27 |
Heey @kaichaosun Otherwise, can you please write step by step how to reproduce the error? Preferably, also with inputs that don't give error so we can compare. |
@gabrielmer will do, thanks for the updates. |
Problem
I'm writing app using Store REST API.
Example endpoint: https://waku.whisperd.tech/store/v1/messages?contentTopics=/universal/1/community/waku,/universal/1/community/status&ascending=false
Using the returned digest somethings got
400 bad request
, error isIncorrect base64 string
:Examples:
https://waku.whisperd.tech/store/v1/messages?contentTopics=/universal/1/community/waku,/universal/1/community/status&ascending=false&pubsubTopic=/waku/2/rs/1/4&digest=4eM/v8m9EGWRDjaKsa+sW41D8exdVrvwj8Uz6ORWs/Q=&senderTime=1713802526605000000&storeTime=1713802526605000000
https://waku.whisperd.tech/store/v1/messages?contentTopics=/universal/1/community/waku,/universal/1/community/status&ascending=false&pubsubTopic=/waku/2/rs/1/4&digest=jXLrLT0Md0zA/YZsVlvsH0RH9yxgrV/Ref3+J/+Ju9g=&senderTime=1713802535971246300&storeTime=1713802535971246300
It sometimes got 400 with the returned cursor, sometimes not.
And seems base64 is not friendly to browser, https://stackoverflow.com/questions/1374753/passing-base64-encoded-strings-in-url
The text was updated successfully, but these errors were encountered: