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. Not having had any bad feedback with
> just the \n (other than not being compliant) I went back to that. Sigh.
>
> However, your solution with just the first line having the \r\n is not
> something I've tried. What made you decide to do just the first line?
I just made the minimal change needed to get this embedded web server
we have working. The server only looks at the first line of the
header, it expects to find \r\n at the end of the line.
> What I will do when I get back from Burning Man is to build a version
> with your fix and then send it to the people that were having problems.
Going to burning man eh. Me too. I will be the guy with the soccer ball.
> If they are happy, then I will apply your patch. If they are not happy,
> I will go with Sean's suggestion and add a checkbox to the options
> dialog.
>
> Sound fair?
The dialog box might be the only way to make everyone happy.
You might also want to auto-detect if the proxy is broken
(does not take \r\n) but going to some known site before
the very first request.
I will be fine with my own local hack. I just need to get
this working for a demo. If anyone is going to ESCW
next month, be sure to stop by the Red Hat booth to see
the "embedded D.J." demo I am putting together (It features
freeamp of course).
later
Mo DeJong
Red Hat Inc
_______________________________________________
[EMAIL PROTECTED]
http://www.freeamp.org/mailman/listinfo/freeamp-dev
