Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

Ampersand trouble #2

Open
TheOddLinguist opened this issue Feb 28, 2012 · 1 comment
Open

Ampersand trouble #2

TheOddLinguist opened this issue Feb 28, 2012 · 1 comment

Comments

@TheOddLinguist
Copy link

When I send a request (POST request for authentication, in this specific case) with an ampersand as part of one of the params, it disappears by the time it gets to my webapp. I'm guessing it's because there's a part of the process that mistakes it as an ampersand in a query string or something like that. Any idea how to get around this issue? Perhaps do some other encode/decode before calling FlyJSONP, like Base64, to avoid the characters? (Although that has equals signs; perhaps that'd be an issue, too?)

@starpause
Copy link

TheOddLinguist, I hope you've solved your problem by now but just in case & for anyone else running into similar: yes, your params are being sent to the server as part of a URL string so any reserved characters need to be encoded. Javascript's built in encodeURI will handle this nicely.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants