-
Describe the bug
No Content-Disposition Header from a GET request. Actual behaviorUsing the browser or node-fetch to any URL, I'm able to retrieve the header "Content-Disposition" correctly. All the resources I've got from Google mentions CORS issues and adjustments on the server that is serving the file, but as I'm running a backend service, I need to download files from servers I have no control whatsoever. Expected behaviorRetrieve the 'content-disposition' from response headers. Code to reproduceconst response = await got(
'https://www.renesas.com/br/en/document/apn/ek-ra2e1-example-project-bundle?language=en',
{ responseType: 'buffer', throwHttpErrors: false }
);
console.log(response.headers['content-disposition']);
... Checklist
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Not a Got issue. The status code is |
Beta Was this translation helpful? Give feedback.
Not a Got issue. The status code is
403
so this is expected - probably you're missing some headers.