asgiref icon indicating copy to clipboard operation
asgiref copied to clipboard

ASGI specification and utilities

Results 62 asgiref issues
Sort by recently updated
recently updated
newest added

- Closes #141 Currently, there are two implementations of HTTP Trailer: - https://github.com/encode/uvicorn/pull/1599/ (Uvicorn) - https://github.com/nonebot/nonecorn/blob/nonecorn_dev/src/hypercorn/protocol/http_stream.py#L232 (Nonecorn - Hypercorn fork) - Commit that introduced it: https://github.com/nonebot/nonecorn/commit/222757f8da25fc5b716b790b93c23710942790b4 What this PR proposes...

It doesn't seem like the current ASGI specification allows applications to send HTTP trailers in their response, since it is indicated that [servers should ignore any further messages on a...

> The `get_running_loop()` function is preferred to `get_event_loop()` in coroutines and callbacks.

ASGI lifespan events are designed to handle setup and subsequent teardown of resource like a database connection, but does not provide any persistence to store this state to requests. Starlette...

It was pointed out in https://code.djangoproject.com/ticket/32586 that the initial ASGI requirement that header names in responses MUST be lowercased - inherited from ASGI 1, I believe - doesn't actually match...

Prompted by https://github.com/encode/starlette/pull/1706#issuecomment-1166522936 The spec currently says: > Sent to the application when a HTTP connection is closed or if receive is called after a response has been sent. After...

For those who just want to use this library for typing their ASGI apps/servers (namely [uvicorn](https://github.com/encode/uvicorn/pull/1460) and [starlette](https://github.com/encode/starlette/issues/1217)), it doesn't make much sense to depend on the entirety of this...

On Starlette, we store a lot of information on the `scope`. Outside the `extensions` scope key. See our auditing: https://github.com/encode/starlette/discussions/1511. Also, right now I'm writing a documentation on how to...

As per https://github.com/django/daphne/issues/264 — Daphne lacks Lifespan support, and shouldn't now be labelled the _reference_ implementation. Just a wording tweak to that effect.