Skip to content

clarify encoding needs#61

Open
r10s wants to merge 1 commit intomainfrom
r10s/clarify-encoding-needs
Open

clarify encoding needs#61
r10s wants to merge 1 commit intomainfrom
r10s/clarify-encoding-needs

Conversation

@r10s
Copy link
Copy Markdown
Member

@r10s r10s commented Oct 8, 2025

better be more concrete on encoding requirements.

encoding = is what is done on android by URLEncoder.encode() - but requires explicit action in OS where the method is addingPercentEncoding(withAllowedCharacters:)

@r10s r10s requested review from adbenitez and link2xt October 8, 2025 09:57
@r10s r10s mentioned this pull request Oct 8, 2025
9 tasks
Comment thread README.md

**IMPORTANT:** `PAYLOAD` **must** be base64 encoded (NOTE: you might still need to URL-encode the base64 string to be a valid URL hash) before passing it to the app in the URL hash.
**IMPORTANT:** `PAYLOAD` **must** be base64 encoded and then url-encoded, including url-encoding the character `=`
(the latter is not always default, but needed as `=` is used as a delimiter in the URL as well as padding in base64)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's not default?

Copy link
Copy Markdown
Member Author

@r10s r10s Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

url-encoding the character = is not default eg on iOS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants