endpoints icon indicating copy to clipboard operation
endpoints copied to clipboard

Lightweight REST api backend framework that automatically maps urls to python modules and classes

Results 50 endpoints issues
Sort by recently updated
recently updated
newest added

Should Endpoints use these for error message? It might be deprecated Links: * [RFC 2616 14.46 Warning](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) * [RFC 2047](https://tools.ietf.org/html/rfc2047) * [Warning](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Warning) - This says [warning header is soon to...

From [the docs](https://asgi.readthedocs.io/en/latest/): > ASGI (Asynchronous Server Gateway Interface) is a spiritual successor to WSGI, intended to provide a standard interface between async-capable Python web servers, frameworks, and applications. Heard...

Currently, we basically make all the interfaces look a bit like a WSGI request, then `http.Request` can use `.environ` and stuff to find information like IP address and host. I...

Now that python2 support has been dropped I think I will add [asyncio](https://docs.python.org/3/library/asyncio-task.html) support with the ASGI interface. After some tests, it looks like I can have the async and...

Right now, if the body is empty then the it won't log the body at all, it would be better to say something like `BODY: ` or something like that,...

Found this in some old application code, could probably be moved into Request core: ```python def parse_user_agent(self, user_agent): """parses any user agent string to the best of its ability and...

Body doesn't have the request id: ``` [I] Request 0c2f934a-f9f5-4ffd-ba6f-4735488587d0 header Accept-Encoding: gzip, deflate, br [D] BODY: {'foo': 1111} ``` ---- The request id could probably be shortened to the...

turns out response body is buried, an error is raised but the server returns a 200 because the headers are already sent before the body is encoded, so all the...

I'm wondering if we can merge Connection and Call together, so Connection would extend our base `call.Call`? The reason why I was thinking about this is because I added a...

so if you pass in `@param("", errmsg=...)` it would use that `errmsg` as the error string if param fails in some way, this would allow us to fine tune client...