-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use Angular 5.2.8 How to get the downloaded file name, which is not the same as Angular 4 #22703
Comments
Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation. |
@chenwuwen Please chek in with 5.2.7 , I think there is a problem in 5.2.8 and 6.0.0-beta.7 . |
Closing this issue as it does not follow the issue template. Please file a new issue that follows the template, which gives the team the information needed to investigate. |
I am getting this same issue. I went from 5.0.2 to 5.2.8 and our oidc-client started to fail to grab the state from the redirect response. Downgrading to 5.2.7 fixed the issue. |
Maybe you can use: This will return the response (with the Blob and Content-Disposition header) and not only the body (Blob). |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I use the angular version is 5.28, now the situation is that I want to download the file server request, I set up the ResponseType Blob before Angular 4, the server returns a Response object which contains a lot of information, I can get the Blob object and the name of the file from which now use Angular5, the Blob object is directly received that can't get file name, how can I do, in order to obtain the file name, thank you
The text was updated successfully, but these errors were encountered: