Closed Bug 1031170 Opened 10 years ago Closed 9 years ago

[RTSP] Follow-up of 1021006 - Server replies error 457 after end-of-stream

Categories

(Firefox OS Graveyard :: RTSP, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.1 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.1 --- affected

People

(Reporter: ethan, Assigned: ethan)

References

Details

(Whiteboard: [2.1-flame-test-run-2])

This is a follow-up of bug 1021006. Steps: 1. Open an RTSP URL in B2G browser to play an audio or video through RTSP streaming. 2. Wait until the media is being played to the end, and the control button becomes "play". 3. Click "play" to re-play the media again. Expected Result: The media can be re-played successfully from the beginning. Bug: An error message "Video playback aborted due to a network error" is shown.
Note that the occurrence of this bug depends on the behaviors of RTSP servers. In my experiment, this bug doesn't happen with DarwinStreamingServer 6.0.3. We can obtain the expected result with such server. However, if we play RTSP from the Youtube/Google RTSP server, it would reply the 457 (Invalid Range) error, which causes the error message appear. We've examined the packet contents of the 1st and 2nd RTSP PLAY requests, they are basically the same. So far we have no idea why the Google RTSP server would reply 457 error.
Assignee: nobody → ettseng
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [2.1-flame-test-run-2]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
No one is actually working on RTSP for FxOS right now.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.