#32240: ConnectionAbortedError should be treated as a broken pipe error in the
development server
-------------------------------------+-------------------------------------
Reporter: Petter | Owner: Petter Strandmark
Strandmark |
Type: | Status: assigned
Uncategorized |
Component: HTTP | Version: 3.1
handling |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
People using Windows have been complaining about very long stack traces in
the development server for a long time:
- https://github.com/python/cpython/pull/9713
- https://bugs.python.org/issue27682
These happen under normal interaction with the development server using
Chrome.
I have fixed one issue in CPython in wsgiref, but I belive that we should
also fix is_broken_pipe_error in django/core/servers/basehttp.py
--
Ticket URL: <https://code.djangoproject.com/ticket/32240>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.d3e416ea2db10f890db4520f66338a90%40djangoproject.com.
