Comment 2 for bug 1320276

Arun Kant (arunkant-uws) wrote :

With curl if Content-Type header is not specified, then curl uses its default Content-Type header which is not expected / support content format from barbican perspective (even though actual content can be json format). So made change to address this case via adding default content-type support for POST, PUT and PATCH methods in case its missing or is passed in as 'application/x-www-form-urlencoded' (not expected content type).

Also just now noticed that there is another similar change: So either of that change will address the above mentioned issue.