We've stumbled upon an issue in regards to include_url that we've isolated to be a Lasso 9 problem.
If we use include_url to send json_serialized data containing non ASCII chars,like =C5=C4=D6=DC the content headers CONTENT_LENGTH is calculated wrong.. Basically counting each double byte char as a single byte. Because of the miscalculation it then cuts of the provided param prematurely.

Here's reproducible code:

sender.lasso
<?LassoScript
local(mymap = map("xc"= "=C5=C4=D6aao"))
local(myjson = json_serialize(#mymap))

include_url('http://boot.dev/dev/target.lasso',
-postparams = #myjson,
-verifypeer,

-string
)
'<hr />'
local(mymap = map("xc"= "AAOaao"))
local(myjson = json_serialize(#mymap))
include_url('http://xxx.yyy/target.lasso',
-postparams = #myjson,
-verifypeer,

-string
)
?>

target.lasso
<?LassoScript
web_request -> postString
?>

Result:
{"xc": "=C5=C4=D6aa
{"xc": "AAOaao"}

Notice how the first test chops of the end of the string. The cutting equals the number of double byte chars in the post param string.

Bypassing include_url and using the curl type directly gives the same result. Whereas constructing a curl call from the command line works.

So seems to be a Lasso 9 issue.

Comments?

HDB
Jolle
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>