-
Notifications
You must be signed in to change notification settings - Fork 56
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
fix: URL encoding for pubsubTopic and contentTopics parameters #3200
Draft
vishwamartur
wants to merge
6
commits into
waku-org:master
Choose a base branch
from
vishwamartur:fix-url-encoding
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Related to waku-org#3128 Update the API to enforce mandatory URL encoding for `pubsubTopic` and `content_topic`. * Update `docs/api/rest-api.md` to include examples of URL-encoded `pubsubTopic` and `contentTopics` parameters. * Modify `waku/waku_api/rest/store/handlers.nim` to validate and enforce URL encoding for `pubsubTopic` and `contentTopics` parameters. * Add error handling for invalid or non-encoded `pubsubTopic` and `contentTopics` parameters in `waku/waku_api/rest/store/handlers.nim`. * Update `decodeRequestBody` function in `waku/waku_api/rest/rest_serdes.nim` to validate and enforce URL encoding for `pubsubTopic` and `contentTopics` parameters. * Add error handling for invalid or non-encoded `pubsubTopic` and `contentTopics` parameters in `waku/waku_api/rest/rest_serdes.nim`.
Ivansete-status
changed the title
Fix URL encoding for pubsubTopic and contentTopics parameters
fix: URL encoding for pubsubTopic and contentTopics parameters
Dec 9, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! I just added a few comments/question
Co-authored-by: Ivan FB <[email protected]>
Co-authored-by: Ivan FB <[email protected]>
Thanks for this @vishwamartur ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #3128
Update the API to enforce mandatory URL encoding for
pubsubTopic
andcontent_topic
.docs/api/rest-api.md
to include examples of URL-encodedpubsubTopic
andcontentTopics
parameters.waku/waku_api/rest/store/handlers.nim
to validate and enforce URL encoding forpubsubTopic
andcontentTopics
parameters.pubsubTopic
andcontentTopics
parameters inwaku/waku_api/rest/store/handlers.nim
.decodeRequestBody
function inwaku/waku_api/rest/rest_serdes.nim
to validate and enforce URL encoding forpubsubTopic
andcontentTopics
parameters.pubsubTopic
andcontentTopics
parameters inwaku/waku_api/rest/rest_serdes.nim
.