Bug 1821 – Softsqueeze BODY frames (used in direct streaming) have extra padding

Bug 1821 - Softsqueeze BODY frames (used in direct streaming) have extra padding

Summary:

Softsqueeze BODY frames (used in direct streaming) have extra padding

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Softsqueeze
Version:	6.0.0
Platform:	PC All

Importance:	P2 normal (vote)
Target Milestone:	Future
Assigned To:	Richard Titmuss

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-07-14 16:16 UTC by Vidur Apparao
Modified:	2008-12-15 13:06 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Vidur Apparao 2005-07-14 16:16:10 UTC

The BODY frames (possibly also the HEAD frames) from Softsqueeze seem to be a
minimum of 1024 bytes in length, padded with NULL bytes. This was causing a
problem for the SqueezeNetwork - the byte buffer for the packet was treated as a
string with embedded NULLs. We'd parse the BODY as a playlist and the last URL
would have the escaped version of the NULLs tacked on at the end. I've fixed the
service's handling of the NULLs, but just wanted to let you know that the extra
bytes were going across the wire.

Comment 1 Blackketter Dean 2005-07-18 08:14:18 UTC

Richard:  did you see this?

Comment 2 Richard Titmuss 2005-07-27 13:51:51 UTC

Hi, yes I have seen it. Sorry been busy with other things lately.

Vidur, I have looked at this tonight and the BODY frames seem the be the correct
length. Can you remember what streams were having problems?

Comment 3 Vidur Apparao 2005-07-27 13:57:46 UTC

I believe it was KCRW Music. You should be able to recreate by connecting SS to
the SqueezeNetwork, choosing it as the current player in the netcontrol and
picking KCRW music from the SqueezeNetwork home page.

Comment 4 James Richardson 2008-12-15 13:06:52 UTC

This bug appears to have been fixed in the latest release!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Make sure to include the version number of the software you are seeing the error with.