> Hi all.
>
> I have been chasing down a little bug that was keeping me
> from using freeamp to pull mp3 files off a web server.
> The odd part was that it worked just fine with winamp
> but when I connected with freeamp the webserver puked
> saying the GET line was invalid.
>
> At any rate, I was able to get the GET method sent
> out by freeamp to work with the sever by adding a
> \r before the \n in the GET line. I think the RFC
> says that you need both \r and \n, but there are
> at least some web servers that are really picky
> about this. This patch was enough to get things
> working. It would really be better to add a \r
> to all the header bits that just use \n now, but
> I will leave that up to you developers.
>
> Mo DeJong
> Red Hat Inc
Lol. I believe that the \r's were recently removed from http lines, due to
it breaking proxy support in some cases. Rob, do you want to comment beyond
bug report 893?
Also, looking into the linux crashes with http streams, I have been able to
reproduce a seg fault on a stream once, although it tends to be stream
specific. None of the streams in the my streams listing cause a crash, so I
have been using http://166.90.143.147:13582/ as my test stream for crash
reproduction. If anyone has a stream which causes freeamp to crash with a
higher frequency than ~ once every 10 sessions, can you pass that on to me?
And, FYI, the test.txt file is a debug log for the Relatable recommended
streams feature, and has no relationship to the actual streaming process.
This could be a result of a frame alignment issue feeding the decoder, but
it doesn't exhibit the same sideband/header corruption that happens in bug
#905.
-Sean Ward
Relatable
_______________________________________________
[EMAIL PROTECTED]
http://www.freeamp.org/mailman/listinfo/freeamp-dev
