#19022: Connection reset by peer with development server.
-------------------------------+--------------------------------------
Reporter: tdhutt@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.4
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
"connection reset '''by peer'''" usually means that the browser closed the
connection prematurely. For instance it happens when you move to new page
while the assets of the previous page are still loading. This is harmless,
it's just how browsers work. There's no point in loading an asset that
isn't necessary any longer.
#18126 talks of using `runserver` in production under high load, this is
definitely something you mustn't do (see the docs).
--
Ticket URL: <https://code.djangoproject.com/ticket/19022#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
