Box Status

400 Error when request header contains empty name value pairs.

フォローする
新規投稿
srinivasareddy.challa-servicenow-demo

Initially when request header contains empty name value pair the rest api was working fine, recently api is throwing 400 bad request error.

We want to know whether Box API has added any latest changes on header validation. We did not find any documentation on such changes, this seems to be unexpected change. Can we get an update on what is modified at Box API end so that we can handle accordingly.

Example- Create Folder API with Post: https://api.box.com/2.0/folders, header: {"name":"","value":""}, Body: { "name" : "test-temp1", "parent" : {"id": "0"} }

0

コメント

1件のコメント

日付 投票
  • Alex Novotny

    Hi! 

    It looks like a box support agent responded the below - which is correct. I will post for other users to see. 

    Unless explicitly stated in our Create folder API endpoint, there should be no additional headers included in the API request. While including additional API request headers or request parameters MAY work we cannot guarantee the API request will succeed. From the Create folder API endpoint there is no documentation regarding including additional headers. Therefore, we have started to tighten the headers and request parameters we have accepted for our API endpoints. Including an empty header will now not work and we require you do not include empty headers in further API requests.

    Thanks, 

    Alex, Box Developer Advocate

    0
    コメントアクション パーマリンク

投稿コメントは受け付けていません。