Closed
Bug 940460
Opened 11 years ago
Closed 10 years ago
[User Story] [RTSP] Cross-protocol redirects from HTTP to RTSP
Categories
(Firefox OS Graveyard :: RTSP, defect)
Tracking
(feature-b2g:2.0, tracking-b2g:backlog)
VERIFIED
FIXED
People
(Reporter: skamat, Unassigned)
References
Details
(Keywords: feature, Whiteboard: [ucid:RTSP1, ft:RIL])
As an operator partner, I would like Cross-protocol redirects from HTTP to RTSP supported
Updated•11 years ago
|
Blocks: b2g-RTSP-1.3
Depends on: 884702
Keywords: feature
Whiteboard: [ucid:RTSP1, 1.3:p2, ft:ril]
Target Milestone: --- → 1.3 Sprint 6 - 12/6
Updated•11 years ago
|
No longer depends on: 884702
Whiteboard: [ucid:RTSP1, 1.3:p2, ft:ril] → [ucid:RTSP1, ft:ril]
Target Milestone: 1.3 Sprint 6 - 12/6 → ---
Updated•11 years ago
|
Whiteboard: [ucid:RTSP1, ft:ril] → [ucid:RTSP1, 1.3:p2,, ft:ril]
Comment 1•11 years ago
|
||
Update whiteboard tag to follow format [ucid:{id}, {release}:p{1,2}, ft:{team-id}]
Whiteboard: [ucid:RTSP1, 1.3:p2,, ft:ril] → [ucid:RTSP1, 1.3:p2,, ft:RIL]
Updated•11 years ago
|
Whiteboard: [ucid:RTSP1, 1.3:p2,, ft:RIL] → [ucid:RTSP1, 1.3:p2, ft:RIL]
Comment 2•11 years ago
|
||
1.4 user story supposedly needs to be complete before Sprint3.
Will communicate with team to reconfirm target milestone.
blocking-b2g: --- → backlog
Whiteboard: [ucid:RTSP1, 1.3:p2, ft:RIL] → [ucid:RTSP1, 1.4, ft:RIL]
Target Milestone: --- → 1.4 S3 (14mar)
Updated•11 years ago
|
Flags: in-moztrap?(whsu)
Comment 6•11 years ago
|
||
According to comment 5, removing the target milestone.
Whiteboard: [ucid:RTSP1, 1.4, ft:RIL] → [ucid:RTSP1, ft:RIL]
Target Milestone: 1.4 S3 (14mar) → ---
Updated•11 years ago
|
Component: General → RTSP
Comment 7•11 years ago
|
||
Do we need to consider "HTTPS" protocol?
Comment 8•11 years ago
|
||
Add test cases. Thanks.
1. https://moztrap.mozilla.org/manage/case/11929/
2. https://moztrap.mozilla.org/manage/case/11928/
3. https://moztrap.mozilla.org/manage/case/11927/
Updated•11 years ago
|
Flags: in-moztrap?(whsu) → in-moztrap+
Comment 9•11 years ago
|
||
(In reply to William Hsu [:whsu] from comment #7)
> Do we need to consider "HTTPS" protocol?
Hi William - as far as the code is concerned, this should be transparent. HTTP and HTTPS redirects should be handled in the same code path that Ethan is working on.
Comment 10•11 years ago
|
||
Roger that. Thanks Steve!
Updated•11 years ago
|
blocking-b2g: 2.0? → backlog
Comment 11•10 years ago
|
||
Hi, Ethan,
Could I have your confirmation?
Have we completed the requirement?
If so, could we mark it as "RESOLVED"?
Thanks.
...Needinfo Ethan
Flags: needinfo?(ettseng)
Comment 12•10 years ago
|
||
(In reply to William Hsu [:whsu] from comment #11)
> Hi, Ethan,
> Could I have your confirmation?
> Have we completed the requirement?
> If so, could we mark it as "RESOLVED"?
> Thanks.
Yes. This bug is actually fixed by bug 992568.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ettseng)
Resolution: --- → FIXED
Comment 13•10 years ago
|
||
Thanks Ethan!
Verified it.
* Build information:
- Gaia e8a08a3f7a608993f0b302371e016e73faceea70
- Gecko https://hg.mozilla.org/mozilla-central/rev/2897fb554990
- BuildID 20140505160203
- Version 32.0a1
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
feature-b2g: --- → 2.0
Updated•10 years ago
|
Blocks: b2g-RTSP-2.0
Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•