On Dec 11, 6:17 pm, Gabriel Genellina [EMAIL PROTECTED]
wrote:
En Tue, 11 Dec 2007 10:51:13 -0300, Object01 [EMAIL PROTECTED] escribi�:
I've been working with the source code for Trac (http://
trac.edgewall.org/) lately and have run across a bizarre problem. It
seems that all POST
On Dec 12, 12:45 pm, Bjoern Schliessmann usenet-
[EMAIL PROTECTED] wrote:
Object01 wrote:
The server is multithreaded, handling each request on its own
thread.
Ugh.
But is a RST really a part of a valid close operation?
Depends on the state of the parties :) The proper way to close
Is this applicable in your
case?:http://brad.livejournal.com/2152593.html?thread=10832273#t10832273
(closing a nonblocking socket with a nonempty output queue generates a RST)
Based on my stepping through the code, everything passed to
_fileobject.write() makes it out onto the wire just fine.
I've been working with the source code for Trac (http://
trac.edgewall.org/) lately and have run across a bizarre problem. It
seems that all POST requests to Trac's standalone server (tracd) have
a random chance of causing the server to issue a TCP RST packet that
resets the connection.
Running
