#36193: AssertionError: Invalid ASGI message after request body: http.request
-------------------------------------+-------------------------------------
Reporter: Dominik Gasparic | Owner: (none)
Type: Bug | Status: closed
Component: HTTP handling | Version: 5.0
Severity: Normal | Resolution: invalid
Keywords: ASGI, | Triage Stage:
http.disconect, | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => invalid
* status: new => closed
Comment:
Hi Dominik, thank you for the ticket
In the issue you raised to Nginx Unit, you mentioned
> The same code works perfectly well with uvicorn and granian so I would
expect it to also work with Unit
This doesn't look like Django is at fault to me.
Please use our [https://docs.djangoproject.com/en/dev/faq/help/#how-
do-i-do-x-why-doesn-t-y-work-where-can-i-go-to-get-help support channels]
for help in identifying the source of the issue. There are volunteers who
can help to figure out what is going on here.
If after further investigation, it is confirmed that Django is at fault,
please re-open with more details.
--
Ticket URL: <https://code.djangoproject.com/ticket/36193#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070195132709d0-a9f9fa41-0ff4-48b6-b041-e5f4d0143a5b-000000%40eu-central-1.amazonses.com.
