Should I url encode them individually? Or just the entire string of
arguments?
On Nov 1, 2012 4:53 AM, "Alan Williamson" <[email protected]> wrote:
> oh you definitely need to URLEncode this url
>
> As good practice, you should always encode every parameter, including the
> firstName/lastName pairs here too.
>
>
> On 31/10/2012 13:50, Jason Allen wrote:
>
>> I'm trying to get an AJAX function working, and it otherwise works except
>> for when one of the included arguments is a string with a bunch of special
>> characters (like a pw).
>>
>> [code]
>>
>> $.getJSON("http://company.com/**access.cfc?method=**
>> checkUserCredentials&userID=<http://company.com/access.cfc?method=checkUserCredentials&userID=>"+
>> #session.myID# + "&lastname=" + lastName + "&firstname=" + firstName+
>> "&email=" + email + "&password=" + password,function(**
>> checkUserCredentialsResults)
>>
>> [/code]
>>
>> This works fine if the password doesn't contain any prohibition/special
>> characters.
>>
>> For instance.. 'test123' works fine, but 'test!@#456' gets truncated to
>> 'test!@'
>>
>> Do I need to encode this url? Or would it be better to post these
>> arguments as form variables to the CFC?
>> --
>> online documentation: http://openbd.org/manual/
>> http://groups.google.com/**group/openbd?hl=en<http://groups.google.com/group/openbd?hl=en>
>>
>
> --
> online documentation: http://openbd.org/manual/
> http://groups.google.com/**group/openbd?hl=en<http://groups.google.com/group/openbd?hl=en>
>
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
