From: John 'f. F. <fes...@n5...> - 2009-02-18 01:22:53
|
I have a problem where yaws is hanging when I POST to it. I've reduced to to basically this request: POST /foo.yaws?text=1 HTTP/1.1 Host: vm32bu.local Content-Type: text/plain Content-Length: 5 Connection: close data note the data has a space in front. " data" if I change the space to something else, things don't hang. we're on yaws 1.77 any clues? will the upgrade help? ;) I'll probably go that route next anyhow, and then into trying to debug more deeply. any help is appreciated. -- fess fe...@n5... 626 771 0045 x 42 there are 54 colored squares on a Rubik's Cube. |
From: Steve V. <vi...@ie...> - 2009-02-18 02:50:49
|
On 2/17/09, John 'fess' Fessenden <fes...@n5...> wrote: > > I have a problem where yaws is hanging when I POST to it. > I've reduced to to basically this request: > > > POST /foo.yaws?text=1 HTTP/1.1 > Host: vm32bu.local > Content-Type: text/plain > Content-Length: 5 > Connection: close > > data > > note the data has a space in front. " data" > if I change the space to something else, things don't hang. Odd. > we're on yaws 1.77 any clues? will the upgrade help? ;) > I'll probably go that route next anyhow, and then into trying to debug > more deeply. any help is appreciated. I took your headers and data exactly as you provided them above and successfully ran it against yaws 1.80 (well, slightly updated from the official release 1.80, latest svn rev 1393). I think the upgrade will help. --steve |
From: John 'f. F. <fes...@n5...> - 2009-02-19 00:41:11
|
On Feb 17, 2009, at 4:50 PM, John 'fess' Fessenden wrote: > > > I have a problem where yaws is hanging when I POST to it. > I've reduced to to basically this request: > > > POST /foo.yaws?text=1 HTTP/1.1 > Host: vm32bu.local > Content-Type: text/plain > Content-Length: 5 > Connection: close > > data > > note the data has a space in front. " data" > if I change the space to something else, things don't hang. > > we're on yaws 1.77 any clues? will the upgrade help? ;) > I'll probably go that route next anyhow, and then into trying to > debug > more deeply. any help is appreciated. well, other problems slowed me from upgrading yaws in our environment, [ that and the we're using embeded mode and yaws.hrl updates the #sconf{} record, so a bit more work is required to our code, suggestions for how to better deal with that in the future are appreciated. ] In any event a brilliant colleague can search the web better than myself. :) and found the problem: http://www.erlang.org/pipermail/erlang-bugs/2008-July/000891.html a bug in inet_drv.c prior to r12b4 we are still prepping our jump to erlang r12 and are currently using r11 --fess -- fess fe...@n5... 626 771 0045 x 42 You've heard of studio 54, it was the cool place to be. This is like network 54. |
From: Claes W. <kl...@ta...> - 2009-02-20 14:09:55
|
John 'fess' Fessenden wrote: > In any event a brilliant colleague can search the web better than > myself. :) and found the problem: > > http://www.erlang.org/pipermail/erlang-bugs/2008-July/000891.html > > a bug in inet_drv.c prior to r12b4 I knew there was something familiar about that first space char on the post. Sigh .... /klacke |