# PUT requests to Suspend account using different content-type on 1.5

**URL:** <https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789>\
**Category:** Development\
**Created:** [2016 年4 月 19 日 03:06 UTC](https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789 "2016-04-19T03:06:25Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

作者： ![citadelgrad](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/citadelgrad/32/121003_2.png) [@citadelgrad](https://meta.discourse.org/u/citadelgrad)\
发布日期： [2016 年4 月 19 日 03:06 UTC](https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789/1 "2016-04-19T03:06:25Z")

</div>

Our site is using Discourse 1.5.1 and I believe our hosting provider upgraded us from 1.4 last week. I have no control over this.

It appears that all API responses from Discourse have the content-type of “application/json”. But I have found that under 1.5 when you issue PUT requests to Suspend an account it now responses with the content-type “text/plain”.

I looked at a number of other PUT requests and they all were using “application/json” so I suspect this was an unintended change.

I’m using the pydiscourse library and until the upgrade didn’t throw any errors for PUT requests. Now every PUT request generates an exception because the library checks the response content-type.

Please let me know if I can provide any additional detail.

 ![](https://global.discourse-cdn.com/meta/original/3X/0/e/0e7ed184dd36e10250a7c9b91118abbfeaca5758.png)

---

_[View the full topic](https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789)._