Infeasible
Status Update
Comments
al...@gmail.com <al...@gmail.com> #3
at...@gmail.com <at...@gmail.com> #4
I am hitting this issue on Android 3.2 on Motorola Xoom.
Is there any workaround for this issue?
In which release is this defect planned to be fixed?
Is there any workaround for this issue?
In which release is this defect planned to be fixed?
ni...@gmail.com <ni...@gmail.com> #5
[Comment deleted]
rk...@gmail.com <rk...@gmail.com> #6
This Issue is fixed in Android 4.0(ICS).
rc...@gmail.com <rc...@gmail.com> #7
[Comment deleted]
fr...@gmail.com <fr...@gmail.com> #8
Hi,
This issues does not seem to be fixed. I have the following conversation between a phone and a server in the attachment. For one situation the stagefright is NOT sending any cookie. For another one it sends a very old cookie.
Regards
This issues does not seem to be fixed. I have the following conversation between a phone and a server in the attachment. For one situation the stagefright is NOT sending any cookie. For another one it sends a very old cookie.
Regards
bl...@gmail.com <bl...@gmail.com> #9
My team and I have also encountered the lack of cookie support for HLS connections issue across Android versions as mentioned above.
Can anyone from the Android team provide insight into the likely fix date for this item ?
Can anyone from the Android team provide insight into the likely fix date for this item ?
pe...@gmail.com <pe...@gmail.com> #10
Dear Android Developers at Google, are there any updates from your side for this bug for 3.x or 4.x? There hasn't been any comments forthis issue for a long time now. HTTP authentication using cookies is a very basic HTTP technology. Please help!
en...@google.com <en...@google.com>
hu...@gmail.com <hu...@gmail.com> #11
My team is facing the same issue, in which the mediaplayer itself send a request with User-Agent="stagefright/..." and it keeps an expired Cookie for all time. As result, our request with new unsettable Cookie value is rejected by Server. Can anyone help?
be...@gmail.com <be...@gmail.com> #12
Can anybody explain me why this issue was marked as Spam? Any updates on the issue?
me...@gmail.com <me...@gmail.com> #13
Why is this marked as spam? I see at least one other report of the same issue which is similarly closed (https://code.google.com/p/android/issues/detail?id=10567 ). The issue doesn't seem to be fixed in at least some installations of 4.3: UA of "SonyC6903 Build/14.2.A.0.290 stagefright/1.2 (Linux;Android 4.3)"
ti...@kom.e-technik.tu-darmstadt.de <ti...@kom.e-technik.tu-darmstadt.de> #14
This issue also applies to 4.4 (Kitkat). When using WebView with HTML5 video tag and playing a protected video (e.g. with basic authentication), StageFright ignores the session cookie, i.e. it doesn't send it to the server. The only workarounds I came across were:
1. Setting the "httpOnly"-Flag for the session cookie to false, which presumably decreases security against XSS attacks. More info here:http://stackoverflow.com/a/16405325
2. Setting authentication parameters in the URL to the video, i.e.https://user:pass@example.org/myvideo.mp4 , which also is no viable solution for obvious reasons.
1. Setting the "httpOnly"-Flag for the session cookie to false, which presumably decreases security against XSS attacks. More info here:
2. Setting authentication parameters in the URL to the video, i.e.
fs...@gmail.com <fs...@gmail.com> #15
I am also hitting this issue. I found it discussed on stackoverflow: http://stackoverflow.com/questions/16310552/do-mobile-browsers-send-httponly-cookies-via-the-html5-audio-tag
I have a web-app which plays media, the media requires authentication cookies which are httpOnly
I have a web-app which plays media, the media requires authentication cookies which are httpOnly
ke...@gmail.com <ke...@gmail.com> #16
Got the same issue...implemented authentication in an app and now media only plays on android versions > 4.0.
On a HTC One X with Android 4.0.4 I get:
E/LiveSession(): failed to load playlist at url 'urlWithoutToken'
E/MediaPlayer(): error (1, -1004)
E/MediaPlayer(): Error (1,-1004)
i don't get why this is marked as spam...
On a HTC One X with Android 4.0.4 I get:
E/LiveSession(): failed to load playlist at url 'urlWithoutToken'
E/MediaPlayer(): error (1, -1004)
E/MediaPlayer(): Error (1,-1004)
i don't get why this is marked as spam...
vi...@gmail.com <vi...@gmail.com> #17
Same issue even on 4.4 Kitkat. How is possible that Google let this critical bug without a fix and marked as spam!.
de...@google.com <de...@google.com> #18
I think #11 was a mistake when bulk editing spam issues.
up...@gmail.com <up...@gmail.com> #19
I had the same problem and disabling HttpOnly or Secure flags on cookies didn't solve the problem on Android 4.2 and 4.4 chrome browser.
Finally I figured the cause. I had a cookie with its value containing special characters colon ( : ) and pipe ( | ). After disabling that cookie with special characters the videos play fine in Android 4.2 and 4.4.
Hope this helps someone.
Finally I figured the cause. I had a cookie with its value containing special characters colon ( : ) and pipe ( | ). After disabling that cookie with special characters the videos play fine in Android 4.2 and 4.4.
Hope this helps someone.
Description
The session is started passing an autentication parameter in the entry-point URL:
and the server replies with a cookie to keep track of subsequent request (m3u8, keys, chunks..). However, the player ignores the cookie and performs any new HTTP request without it (therefore the server refuses connection, since they are unauthorized). This make it impossible to implement services with (even basic) content protection.
The MediaPlayer is expected to support all HTTP standard features, including cookies.
Device info:
Android 3.0.1 on Galaxy Tab 10.1
Android 3.1 on Motorola Xoom