-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Header #49
Comments
Hi Akhil,
Do you have a solution for this? If so, send me the pull request.
It would also be good if you could share the exact steps that you are
trying to do with example.
Thanks.
Best Regards,
Vijayendra
…On Wed, 25 Mar 2020, 14:40 Akhil A Ambady, ***@***.***> wrote:
Thanks for developing this component.
I'm using your ngx-audio-player for streaming audio from URL.
The player is working fine. I need to know how to add authorized token to
header for the URL.
This is to stream the audio file which is the response from an API which
is authorized.
So it would be great if you address this issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/vmudigal/ngx-audio-player/issues/49>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALV5ZWVAK3BA2OUQCKH6Z3RJIJV3ANCNFSM4LTP7VBA>
.
|
No, I don't have a solution for this. I would like to know whether we can add an authorized token with header. Thanks. Best Regards, |
Just checking if there is any update on this issue. Or we have to build it referencing https://auth0.com/blog/building-an-audio-player-app-with-angular-and-rxjs/ |
I wasn't able to find any solutions for this. Looks like the only option at this point, is downloading the file using your own API requests, and then pointing the player to the downloaded file. |
Thanks for developing this component.
I'm using your ngx-audio-player for streaming audio from URL.
The player is working fine. I need to know how to add authorized token to header for the URL.
This is to stream the audio file which is the response from an API which is authorized.
So it would be great if you address this issue.
The text was updated successfully, but these errors were encountered: