Closed dbeecham closed 4 years ago
I've experienced that same error sequence in using a more complex server from standard Windows browsers, on the Windows platform, and haven't a clue where to look to discover the problem. For me it is intermitant and doesn't seem to cause serious issues, something must retry.
But it looks like you get this on some Linux platform? Is it 100% reproducible? If so, this could be a great step towards understanding and solving the problem.
If that's a bug, then in python wsgiref, not in bottle. Not much we can do about that. Looks like the client disconnected too early (probably because of -f
) and wsgiref failed to write the response to the socket, and then failed at handling that error. Bottle is no longer involved at that point.
I got this error when running
against this server