Hi all,

The old behaviour (before 3 December):

- Download requests had to have "Accept: application/json" or no accept header.

- The response would be "Content-Type: application/json" although the actual content would be text like "0000077-181127163650858"

From 3 December until now was only text/plain.

New behaviour (as from a few minutes ago):

- Download requests can have either "Accept: application/json", "Accept: text/plain", or no accept header at all.

- The response Content-Type will be the same as the Accept header, or text/plain if there was none.

That should fix the original problem [1], but remain compatible for libraries that currently have a workaround for the current behaviour.

Cheers,

Matt

[1] https://lists.gbif.org/pipermail/api-users/2017-May/000457.html

On 04/12/2018 08:37, Federico Mendez wrote:

Scott, sorry for that breaking change, but we have changed the response type of “/v1/occurrence/download/request” It was incorrectly set to respond with JSON when in reality returns “text/plain” (a download key or identifier). If possible please change the response in the rgbif package. Please let us know if that fixes the issue and if we can assist you in any other way.

Best, Federico.

On 04/12/2018, 00.07, "API-users on behalf of Scott Chamberlain" <api-users-bounces@lists.gbif.org on behalf of myrmecocystus@gmail.com> wrote:

 Hi,

 The occurrence download API has been throwing 406 errors for some users

 https://github.com/ropensci/rgbif/issues/333

 I concur that it happens for me as well.

 Has anything changed in the backend for the downloads route?

 Best, Scott
 _______________________________________________
 API-users mailing list
 API-users@lists.gbif.org
 https://lists.gbif.org/mailman/listinfo/api-users

---

API-users mailing list API-users@lists.gbif.org https://lists.gbif.org/mailman/listinfo/api-users