dojo/request/iframe not working as expected with response header: 'Content-Disposition: attachment'

[burrito__]

When making a post request with dojo/request/iframe to a web service which returns Content-disposition: attachment in the header, the following behaviour is observed

1) request is made to the server and the browser interprets the response as a file download 2) The returned promise from the post() function is never completed. 3) subsequent post() requests made via iframe are not executed.

Test case and php script attached.

[burrito__]

php script for creating csv file download

[burrito__]

Test case for iframe behavior

[burrito__]

workaround for the same use case using dijit/form/Form

[cjolif]

some of our internal users are facing that one as well.

[Bryan Forbes]

This is a tricky one. When the server returns Content-Disposition: attachment, the iframe's load event will not fire in Chrome, Safari, or Firefox 3.5+. In addition, the iframe cannot be reused. There are a couple of work-arounds which I'll try to explore, but it looks like the best way will be to require users to have their server set a cookie which we'll have to periodically check.

[dylan]

Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.