Hi Vijitha,
What if the backend expects the x-www-form-urlencoded type payload? In that
case, we can't use multipart/form-data.
Thanks,
Keerthika.
On Thu, Jan 4, 2018 at 1:18 PM, Vijitha Ekanayake wrote:
> Hi Senduran,
>
> AFAIK, There is no standard documentation on how to convert JSON to
> x
Hi Senduran,
AFAIK, There is no standard documentation on how to convert JSON to
x-www-form-urlencoded format as key-value pairs. As mentioned by Thusitha,
When the JSON is getting complicated converting it to the
x-www-form-urlencoded will also become complicated and may lead to
inconsistencies o
Hi Senduran,
IMHO x-www-form-urlencodedis for simple key value pairs. When the payload
is complicated, we should use multipart/form-data instead of
x-www-form-urlencoded content type. It can handle any complex complex
scenarios that you mentioned.
Thanks
Thusitha
On Wed, Jan 3, 2018 at 4:50 PM,
Hi all,
When an XML or a JSON is converted to x-www-form-urlencoded format the key
value pair is created.
i.e
value1
value2
will be converted to key1=value&key2=value2
similarly
{"key1" : "value1", "key2" : "value2"} also get converted to
key1=value&key2=value2
But what if the XML or J
