James Eshelman wrote: > I have a special purpose http server made from HTTP::Daemon... [...] > > Failure scenario: > -No IE window open on the server host: > -create the server; > -open the startup window for the process in IE (i.e. open an html > startup file on the local file system) to GET the config file from the > server ; > -loop the server waiting for a connection and request; > -send the http GET request (i.e. SUBMIT the form with the desired > filename filled in); > = NOTHING, no request is ever received by the server!
If you open another browser window and issue another request to your HTTP::Daemon server, will the earlier request then get processed? If so, then I've observed the same problem with HTTP::Daemon on Win32 and Mozilla family browsers. In my observation the problem is intermittent, and I never did track down the cause. It appeared to be a low-level problem with the socket I/O, such as the accept() call not returning when it should or something buggy in the listen queue. I remember playing around with the Listen attribute to the IO::Socket::INET constructor, but without luck. Though maybe the problem is specific to HTTP::Daemon, as I have an SMTP proxy that uses IO::Socket::INET on Win32 and doesn't seem to suffer from this. -Tom _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
