JSON, URL-encode, and UTF-8

Monte Goulding monte at sweattechnologies.com
Fri Aug 21 01:50:24 CEST 2015


What happens if you comment out line 247 of revLibURL stack script? textEncode native here seems to be a rather dangerous thing to do…

> On 21 Aug 2015, at 9:45 am, Dave Cragg <dcragg at lacscentre.co.uk> wrote:
> 
> 
>> On 21 Aug 2015, at 00:33, J. Landman Gay <jacque at hyperactivesw.com> wrote:
>> 
>> On 8/20/2015 6:25 PM, Peter W A Wood wrote:
>> 
>>> You’re content is no longer valid JSON once you have inserted the
>>> “json=“ (at the PHP developer’s request). There may be a conflict
>>> between the header and the actual content. What happens if you remove
>>> the line setting the httpHeaders?
>> 
>> Thanks Peter. No change, it still fails. I think the PHP guy is stripping off the "json=" anyway and just grabbing the parameters. But it does work without the header in LC 6.
> 
> What happens if you remove the httpHeader setting and also UrlEncode tData? 
> 
> Dave
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the use-livecode mailing list