Form Export Data API - Previous token issue

Developers
1

Hello all,

There seems to be an issue with the "Form Data Export" API. According
to the documentation (https://confluence.dimagi.com/display/
commcarepublic/Export+API), there's an "X-CommCareHQ-Export-Token"
header which is supposed to be sent in the response headers. However,
it looks like the token is not being sent at all.

On using something like this:
https://www.commcarehq.org/a/domain-here/reports/export/?export_tag="http://openrosa.org/formdesigner/4ABC07FF-2434-40B3-B151-D2EBE2F4FB4F"&format=raw

These are the headers which are being sent now:

Connection: Keep-Alive
Content-Disposition: attachment; filename=http://openrosa.org/
formdesigner/4ABC07FF-2434-40B3-B151-D2EBE2F4FB4F.zip
Content-Language: en
Content-Type: application/zip
HTTP_X_OPENROSA_VERSION: 1.0
Keep-Alive: timeout=600, max=100
Server: localhost
Transfer-Encoding: chunked
Vary: Accept-Language,Cookie
Via: 1.

The content is downloaded properly (a zip of XMLs). So, the
authentication is fine. Any ideas?

Thanks,
Aravind

··· Date: Fri, 03 Feb 2012 11:08:28 GMT
2

Hey,

There seems to be an issue with the "Form Data Export" API. According

to the documentation (https://confluence.dimagi.com/display/
commcarepublic/Export+API), there's an "X-CommCareHQ-Export-Token"
header which is supposed to be sent in the response headers. However,
it looks like the token is not being sent at all.

On using something like this:

https://www.commcarehq.org/a/domain-here/reports/export/?export_tag="http://openrosa.org/formdesigner/4ABC07FF-2434-40B3-B151-D2EBE2F4FB4F"&format=raw

Unfortunately, the export tokens aren't yet compatible with the "raw"
export format. I've updated the documentation on the wiki to reflect this.

thanks,
Cory

3

Unfortunately, the export tokens aren't yet compatible with the "raw"
export format. I've updated the documentation on the wiki to reflect this.

Alright, thank you very much, Cory.

Cheers,
Arvind

··· On Wed, Feb 8, 2012 at 12:07 AM, Cory Zue wrote: