{"id":520,"date":"2014-09-30T14:55:22","date_gmt":"2014-09-30T13:55:22","guid":{"rendered":"http:\/\/www.ree7.fr\/blog\/?p=520"},"modified":"2022-08-08T06:47:41","modified_gmt":"2022-08-08T05:47:41","slug":"formurlencodedcontent-with-support-for-array-values","status":"publish","type":"post","link":"http:\/\/www.ree7.fr\/blog\/2014\/09\/formurlencodedcontent-with-support-for-array-values\/","title":{"rendered":"FormUrlEncodedContent with support for array values"},"content":{"rendered":"

As convenient as System.Web.Http is for .NET developers, while working on my current project, I discovered that it did not support array values out of the box.
\nWhen you want to post something in the ‘x-www-form-urlencoded’ form, and using the FormUrlEncodedContent class, you are limited to string keys and values as FormUrlEncodedContent is build out of an IEnumerable<KeyValuePair<string, string>> (or more commonly a Dictionary<string, string>) object.<\/p>\n

What if I want to send an array like :
\nPOST http:\/\/dev.someserver.fr\/0.2\/theaters\/set HTTP\/1.1
\nAccept: *\/*
\nContent-Length: 40
\nAccept-Encoding: identity
\nConnection: Keep-Alive
\nCache-Control: no-cache
\nContent-Type: application\/x-www-form-urlencoded
\nUser-Agent: NativeHost
\nHost: dev.cinetime.fr
\nPragma: no-cache
\ntheaters=[\"LI38249\",\"LI20271\",\"LI20306\"]<\/code><\/p>\n

Well you can’t. Or you could rewrite and extend FormUrlEncodedContent.
\nOr you could just reuse the following gist, because that’s precisely what I’ve done :<\/p>\n