fix truncated query strings in ref URLs#14
Open
filip1 wants to merge 1 commit into
Open
Conversation
When the widget is embedded on a URL containing a query string such as https://example.com/path?foo=1&bar=2, the widget[ref] parameter that gets sent on form submission and saved as "ref" in the database is truncated before the first "=" character. That means it gets stored as https://example.com/path?foo I think that wrapping the URL string in encodeURIComponent() before appending it to the serialized form should fix the issue.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When the widget is embedded on a URL containing a query string such as https://example.com/path?foo=1&bar=2, the widget[ref] parameter that gets sent on form submission and saved as "ref" in the database is truncated before the first "=" character. That means it gets stored as https://example.com/path?foo
I think that wrapping the URL string in encodeURIComponent() before appending it to the serialized form should fix the issue.