Hi Kevin,
I am afraid you will have to give more details and preferably something isolated that we can execute against a standard Seaside installation that exposes your problem.
In my image (very recent Pharo 3, Zinc & Seaside 3.1) your last URL is parsed correctly, both to WAUrl as to ZnUrl:
'http://localhost:8080/appName?action=<actionName>&firstParameter=["Value"]&secondParameter=["Value"]&lastParameter={ "Key":["firstValue","secondValue"]}' seasideUrl queryFields.
=>
a WARequestFields('action'->'<actionName>' 'firstParameter'->'["Value"]' 'secondParameter'->'["Value"]' 'lastParameter'->'{ "Key":["firstValue","secondValue"]}')
'http://localhost:8080/appName?action=<actionName>&firstParameter=["Value"]&secondParameter=["Value"]&lastParameter={ "Key":["firstValue","secondValue"]}' asZnUrl query.
=>
a ZnMultiValueDictionary('action'->'<actionName>' 'firstParameter'->'["Value"]' 'lastParameter'->'{ "Key":["firstValue","secondValue"]}' 'secondParameter'->'["Value"]' )
Sven
On 06 Mar 2014, at 14:49, lanvin.kevin at laposte.net wrote:
> Sorry for multiple copies.
>>>> Hello
>> I am using a REST API in my web application and I have a problem with the http version.
>>>> when I do this kind of request, everything is ok :
>> localhost:8080/appName?action=<actionName>&firstParameter=["Value"]&secondParameter=["Value"]&lastParameter={}
>> Parameters are JSON strings.
>>>> Now if I just change the last parameter as following, the ZnUnknownHttpVersion error is raised.
> localhost:8080/appName?action=<actionName>&firstParameter=["Value"]&secondParameter=["Value"]&lastParameter={ "Key":["firstValue","secondValue"]}
>>>> Every special character is converted to %.. excepting ':' .
>> Thank you
>> _______________________________________________
> seaside mailing list
>seaside at lists.squeakfoundation.org>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside