Thank you but it doesn't appear to be relevant. I connect to app locally (runserver on 127.0.0.1 --- loopback) using 1 browser. There is exactly 1 connection. I can see all requests made to runserver. Sorry I didn't mention it before. I assumed that runserver implies that it runs locally in controlled environment for debugging.
All possible causes mentioned in the link are totally irrelevant for my scenario (runserver on loopback + 1 browser): "no space on the socket queue", "data retransmittion fails", "system timeouts". All user suggestions involve pinging hosts, routers, tracing routs, and so on. I didn't see this problem before. It started when I enabled cache and enabled CACHE_MIDDLEWARE_GZIP for local debugging --- I started to have some problems with this configuration on "production" web site. Maybe this bug is a reflection of something going wrong. That's what I am trying to understand. Thanks, Eugene "paolo" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Eugene Lazutkin wrote: > [cut[ >> error: (10053, 'Software caused connection abort') > > "This error can occur when the local network system aborts a > connection, such as when Winsock closes an established connection after > data retransmission fails (receiver never acknowledges data sent on a > datastream socket).", Django is not the source of the problem. > (http://www.sockets.com/err_lst1.htm#WSAECONNABORTED) > > There are a lot of people asking for help on the net about this(google > for it), and actually it seems that a "standard" remedy doesn't exist. > > HTH
