Re: GET problem tracked down (patch included)

2000-08-28 Thread Phil Chu
[EMAIL PROTECTED] wrote: > > Groan is right. At first I had everything with just \n. Then someone > pointed out that the HTTP spec calls for \r\n. I checked it out and > agreed and applied the change. Then people started reporting that it was > not working with proxies anymore. Not having had any

Re: GET problem tracked down (patch included)

2000-08-27 Thread shren
On Sun, 27 Aug 2000, Blake Winton wrote: > * shren <[EMAIL PROTECTED]> [000827 03:24]: > > On Sat, 26 Aug 2000 [EMAIL PROTECTED] wrote: > > > Sound fair? > > Sounds bad. Going to a broken version of the standard just because > > other programs are broken is a bad idea. It is "\r\n". Changing

Re: GET problem tracked down (patch included)

2000-08-27 Thread Mark B. Elrod
I agree with this... "be strict in what you produce, lenient in what you accept" right? elrod shren wrote: > On Sat, 26 Aug 2000 [EMAIL PROTECTED] wrote: > > > Sound fair? > > Sounds bad. Going to a broken version of the standard just because > other programs are broken is a bad idea. It is

Re: GET problem tracked down (patch included)

2000-08-27 Thread Blake Winton
* shren <[EMAIL PROTECTED]> [000827 03:24]: > On Sat, 26 Aug 2000 [EMAIL PROTECTED] wrote: > > Sound fair? > Sounds bad. Going to a broken version of the standard just because > other programs are broken is a bad idea. It is "\r\n". Changing it to > anything else will cause lots of problems i

Re: GET problem tracked down (patch included)

2000-08-27 Thread shren
On Sat, 26 Aug 2000 [EMAIL PROTECTED] wrote: > Sound fair? Sounds bad. Going to a broken version of the standard just because other programs are broken is a bad idea. It is "\r\n". Changing it to anything else will cause lots of problems in the future.

Re: GET problem tracked down (patch included)

2000-08-26 Thread Mo DeJong
On Sat, 26 Aug 2000, Sean Ward wrote: > > That is the part I don't get. When freeamp crashes on me, it > > is before the stream gets downloaded. I have a little network > > monitor applet that tells me how much data is moving over the > > network interface, and it shows 0 Kbits. Freeamp just hose

Re: GET problem tracked down (patch included)

2000-08-26 Thread Mo DeJong
On Sat, 26 Aug 2000 [EMAIL PROTECTED] wrote: > Groan is right. At first I had everything with just \n. Then someone > pointed out that the HTTP spec calls for \r\n. I checked it out and > agreed and applied the change. Then people started reporting that it was > not working with proxies anymore.

Re: GET problem tracked down (patch included)

2000-08-26 Thread rob
On 26 Aug, Mo DeJong wrote: > 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 in

Re: GET problem tracked down (patch included)

2000-08-26 Thread Sean Ward
> Groan. Yep :(. The real solution will probably be to add a new check box to toggle between using the extra \r or not, as a fix for bad proxies. > That is the part I don't get. When freeamp crashes on me, it > is before the stream gets downloaded. I have a little network > monitor applet that te

Re: GET problem tracked down (patch included)

2000-08-26 Thread Mo DeJong
On Sat, 26 Aug 2000, Sean Ward wrote: > > > 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 > >

Re: GET problem tracked down (patch included)

2000-08-26 Thread Sean Ward
> 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 wa