Child Item

500 Internal Server Error - /2/team/features/get_values

Hi,

I've been experienceing some issues with the following api call today and was wondering if any one could help

POST:

POST https://api.dropboxapi.com/2/team/features/get_values HTTP/1.1
Authorization: Bearer omitted
User-Agent: OfficialDropboxDotNetSDKv2/6.37.0.0
Content-Type: application/json; charset=utf-8
Host: api.dropboxapi.com
Request-Id: |3cdc2381-418052c2c679c059.
Content-Length: 49

{"features":[{".tag":"has_team_shared_dropbox"}]}

HTTP/1.1 500 Internal Server Error
Content-Type: text/plain; charset=utf-8
Cache-Control: no-cache
Content-Security-Policy: sandbox allow-forms allow-scripts
X-Content-Type-Options: nosniff
Date: Fri, 14 Jun 2024 12:58:36 GMT
Server: envoy
Content-Length: 0
X-Dropbox-Response-Origin: far_remote
X-Dropbox-Request-Id: 6d732fa220914a2ca872f24fd6a2bf91

I've also tried the same token in the api explorer and get the same.

Thanks

Find more posts tagged with

Developers

Accepted answers

Greg-DB

@awb Thanks for confirming this is working now! I don't have more specific information on what change the team made though; they identified an issue and adjusted the server code accordingly.

All comments

Greg-DB

Thanks for the report. Can you confirm if you're still seeing this now? If so, about what percent of these calls are failing like this for you? Thanks in advance!

awb

From the testing I have done 100% we use PKCE if this helps

Greg-DB

@awb Just to clarify, do you mean that you are still seeing this error now if you try again now?

awb

Literally just tried before posting reply. Still see this error

Greg-DB

Thanks for confirming. I'm raising this with the team and I'll follow up here once I have any update to share.

awb

Thanks, much appreciated

Здравко

@awb wrote:
...
POST:
POST https://api.dropboxapi.com/2/team/features/get_values HTTP/1.1
Authorization: Bearer omitted
...

Hi @awb,

I was surprised that Dropbox tolerates such a protocol mistake. The requests fail on Dropbox API servers because of much smaller mistakes.

How actually did you construct such a request? 🧐 The supported .Net SDK doesn't do this.

Hm..🤔 Or maybe it's some sort of your copy/paste mistake like the missing separator between request header and request body.

If you have used your custom HTTP client, you may need to check how correct is its work! And if so, does your issue disappear when you use the default HTTP client (i.e. without setting custom one)?

Hope this gives directions to check different possible issue sources.

Greg-DB

Thanks for pointing that out Здравко.

@awb Can you confirm if this is actually how your request is formatted? As Здравко mentioned, that start line shouldn't contain the host name like that.

In any case, we're made an adjustment on the server that may be related to the error you're seeing. Can you try again and let me know if you're still seeing this issue?

awb

@gr @Здравко

The above I believe was captured through fiddler or dumped to out logging mechanism

This all looks to be working as expected our end, no changes were made. Would it be possible to find out what change was made?

Thanks both

Здравко

@Greg-DB, Just to avoid confusion: I don't think that's the issue source (or it's unlikely at least). Usually such URLs (instead of Paths) are used in context of proxy. For better understanding the issue, it's good idea to be posted some binary dump (that will let issue reproduction - eventually), I think.

Greg-DB

@awb Thanks for confirming this is working now! I don't have more specific information on what change the team made though; they identified an issue and adjusted the server code accordingly.