id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 18048,Test client implicitly assuming data to be querystring,johan@…,Johan Sommerfeld,"In some of the request methods (get, head, options, delete) the data input is assumed to be used as querystring input. This makes the client break when sending data such as a json string since ''urlencode'' assumes data to be a ''dict'' This has been solved for some methods. In #11371 for the put request, where the solution was that ''urlencode'' was removed and querystring was only extracted from the path with ''urlparse''. The methods have a lot of redundant code, wehre as it is mostly the setting of content-length and such, this could be consolidated to one function wheras we could keep the possibility to send querystring as a dict into data with the content_type set to some dummy type such as ""querystring"". This aproach would be benefitial since we then allow the test client to send a body with all request, which is as far as I know not forbidden according to the rfc:2616 (I'm no expert in reading rfcs if I'm wrong pleas correct me). ",Bug,closed,Testing framework,1.4,Normal,duplicate,test client,,Unreviewed,1,0,0,0,0,0