Webware for Python

Have you guys ever experienced a problem where loading a Webware-servlet 
will cause the browser to sit there waiting for data forever?

The Servlet executes and sends all the data properly, but the browser, for 
some reason, thinks there's more coming and waits until it times out. I 
think the browser is getting all the data too, but there's something about 
the connection that's not kosher. Firefox tends to be more robust when this 
happens, and usually doesn't ignores it, but IE and Opera will die every 
time.

Could this be related to some kind of Appserver->Mod_Webkit->Apache 
communication problem? I'm not sure how I'd go about debugging this, and 
it's happened to me on a number of occasions. Again, cause or solution 
UNKNOWN. :)

I'm running Apache 1.3.27 for Win32 with mod_webkit 0.5.0 and Webware 
0.8.1.

Re: [Webware-discuss] Also, weird glitchy thing.... From: Jason Hildebrand <jason@pe...> - 2004-04-15 14:52 On Mon, 2004-04-12 at 19:20, Chris Gahan wrote: > Have you guys ever experienced a problem where loading a Webware- > servlet > will cause the browser to sit there waiting for data forever? > The Servlet executes and sends all the data properly, but the > browser, for > some reason, thinks there's more coming and waits until it times out. > I > think the browser is getting all the data too, but there's something > about > the connection that's not kosher. The only time I've had this happen to me was when serving up images and converting/scaling them on-the-fly. I was inadvertently sending an incorrect Content-Length header. Webware completed the request, but the browser was waiting for more. The error became obvious when I tried requesting the image using 'wget' -- so if possible try that out. peace, Jason

[Webware-discuss] Re: Also, weird glitchy thing.... From: Chris Gahan <chris@il...> - 2004-04-17 04:34 On 15 Apr 2004, Jason Hildebrand said: > On Mon, 2004-04-12 at 19:20, Chris Gahan wrote: >> Have you guys ever experienced a problem where loading a Webware- >> servlet will cause the browser to sit there waiting for data >> forever? > > The only time I've had this happen to me was when serving up images > and converting/scaling them on-the-fly. I was inadvertently sending > an incorrect Content-Length header. Webware completed the request, > but the browser was waiting for more. The error became obvious when I > tried requesting the image using 'wget' -- so if possible try that out. I just figured it out. It wasn't a webware thing at all. :) DAYEM. Ah well. Thanks for the help.

1 message has been excluded from this view by a project administrator.