Skip to content
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

How we can get the response header in Exoplayer. #4615

Closed
arishvarunmishra opened this issue Aug 3, 2018 · 4 comments
Closed

How we can get the response header in Exoplayer. #4615

arishvarunmishra opened this issue Aug 3, 2018 · 4 comments
Assignees
Labels

Comments

@arishvarunmishra
Copy link

Actual I am using Exoplayer v2 and on LA_Url request i have to read response header but did not find any way to achieve it.
Also need to acess every response header to stop the video at specific header value.
provide the solution.
While debugging i can access response using - //DataSource.connection.delegate.httpEngine.networkResponse.headers.namesAndValues;

@andrewlewis andrewlewis self-assigned this Aug 6, 2018
@andrewlewis
Copy link
Collaborator

Does HttpDataSource.getResponseHeaders provide the information you need?

@tonihei
Copy link
Collaborator

tonihei commented Aug 6, 2018 via email

@arishvarunmishra
Copy link
Author

arishvarunmishra commented Aug 6, 2018 via email

@ojw28
Copy link
Contributor

ojw28 commented Aug 7, 2018

You need to call getResponseHeaders whilst the connection is open (i.e. between open and close). This has been clarified in the Javadoc on our dev-v2 branch.

ojw28 pushed a commit that referenced this issue Aug 24, 2018
The response headers of the last load are available from the loading source
when creating media source events and can be easily forwarded.

Issue:#4361
Issue:#4615

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=209900693
@google google locked and limited conversation to collaborators Jan 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants