com.dropbox.core.BadResponseException: missing HTTP header "Retry-After"

[morgang-everlaw]

We recently (last few days?) started getting this exception frequently when downloading files using the Java SDK. Relevant stack trace here:

com.dropbox.core.BadResponseException: missing HTTP header "Retry-After"
        at com.dropbox.core.DbxRequestUtil.getFirstHeader(DbxRequestUtil.java:529)
        at com.dropbox.core.DbxRequestUtil.unexpectedStatus(DbxRequestUtil.java:387)
        at com.dropbox.core.v2.DbxRawClientV2$2.execute(DbxRawClientV2.java:226)
        at com.dropbox.core.v2.DbxRawClientV2$2.execute(DbxRawClientV2.java:192)
        at com.dropbox.core.v2.DbxRawClientV2.executeRetriable(DbxRawClientV2.java:330)
        at com.dropbox.core.v2.DbxRawClientV2.executeRetriableWithRefresh(DbxRawClientV2.java:351)
        at com.dropbox.core.v2.DbxRawClientV2.downloadStyle(DbxRawClientV2.java:192)
        at com.dropbox.core.v2.files.DbxUserFilesRequests.download(DbxUserFilesRequests.java:1240)
        at com.dropbox.core.v2.files.DownloadBuilder.start(DownloadBuilder.java:76)

The developer documentation implies that it's valid for a 429 to not include a Retry-After header ("Rate limit responses from the Dropbox API may include a Retry-After header") so it seems like this is an issue with the SDK's response parsing?

I thought this was an issue with the SDK version we were on (7.0.0) but I updated to 8.0.2 and I'm seeing the exact same issue.

[ineil-dbx]

Hi @morgang-everlaw, I was able to reproduce the issue you're encountering, and I've raised it with our engineering team for investigation. Please note that I'm unable to provide an estimated timeframe for this case. However, I'll keep you updated and let you know as soon as I hear anything from the engineering team.