Bug 10362 - Streaming fails when a stream is scanned w/ HTTP 200, but played w/ HTTP redirect
: Streaming fails when a stream is scanned w/ HTTP 200, but played w/ HTTP redi...
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming To SlimServer
: unspecified
: Other Ubuntu Linux
: P3 normal (vote)
: 8.0.1
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-17 04:00 UTC by Manoj Kasichainula
Modified: 2009-06-09 16:14 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manoj Kasichainula 2008-12-17 04:00:05 UTC
As promised (and much delayed, because I wanted to reproduce one more time, but since I don't use that alarm playlist anymore, I won't be), my theory as to why streams fail to play in some cases:

See https://bugs-archive.lyrion.org/show_bug.cgi?id=9534 and especially the attached log files from it. What seems to happen (at least as of SC 7.2, maybe later) is that when it tries to play a playlist, it hits every URL in the playlist, gets its content type and other info, and adds it to the db. Then it picks one to play.

If the initial scan of a stream returns a 200, but the actual play attempt returns a redirect, SC will try to redirect to the Location: URL, as it should. But the code expects the URL to be in the db, so it fails to instruct the squeezebox to stream and ends up in never never land.

As reported in the other bug, the alarm code doesn't detect the lack of playback, and thus the alarm doesn't resort to any of the backup alarm strategies. But, this bug is about the failure to play a stream in this case.

I'm not actually sure that this bug is still present in newer versions (because I think it only gets triggered at times when I use it as an alarm, and I need a more reliable alarm, so I don't test this anymore). I've seen no indication that this bug was fixed though.
Comment 1 Chris Owens 2009-03-16 09:43:33 UTC
We are now planning to make a 7.3.3 release.  Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future.

Thanks!
Comment 2 Chris Owens 2009-03-30 17:31:26 UTC
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out.  If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it.

Thanks.
Comment 3 Chris Owens 2009-03-31 08:53:51 UTC
For some reason Bugzilla did not change the target when I did this yesterday.  Or maybe it was me.  In either case, I'm trying it again.