tall cove
The browser response headers shows the content-disposition header, but when console logging the response headers it appears to be missing.
The expected behavior using 'Content-Disposition' "attachment" type is that the browser save dialog appears, but it does not. (at least not in Chrome at time of writing this..)
Please inform us about adding the 'Access-Control-Expose-Headers': 'Content-Disposition' header in the docs for StreamableFile.
latent rover
There is a doc around adding response headers already. Should be applied here as well
fervent basalt
set exposeHeaders in cors according to the cors doc and nestjs cors configuration
tall cove
The expected behavior using 'Content-Disposition' "attachment" type is that the browser save dialog appears, but it does not. (at least not in Chrome at time of writing this..)
This is according to https://httpwg.org/specs/rfc6266.html#disposition.type, but I am seeing many posts (internet) requiring additional frontend hacks to trigger the Save as Dialog.
sturdy veldt
Content-Disposition is being exposed without the need of adding it to the CORs middleware. However, when I reach out that endpoint via Axios that header is not available, any idea why?
