Valentin V. Bartenev
Valentin V. Bartenev
> Because Nginx Unit puts the full path in the PATH_INFO variable, a Django application accessible at a non-root path such as /django must be configured to strip /django from...
> Implementing my request (or something similar) would allow applications to be run under both Nginx Unit and Apache with no modifications. Sure, understood. But what I dislike with `SCRIPT_NAME`...
Unit doesn't support chunked transfer encoding in requests for the moment. So, the only options right now is to specify the Content-Length.
@mafin It needs to be changed on the client. There's no way to control client's request `Transfer-Encoding` from the server side.
Here's some PoC: https://gist.github.com/VBart/ce0bad1f15a337eff49f1336311d8381 ``` % build/njs -c "var a = ['a', 'b', 'c']; for (var e of a) console.log(e);" a b c ```
@krburkhart the event, that would help to gracefully resolve this situation was discussed here: https://github.com/django/asgiref/pull/199
@thresheek there're still users who prefer to stay with LTS release. I don't see reasons why we should discriminate them and don't build a module for all available python versions...
@hongzhidao Could you elaborate how 2 should help to implement 3? These structures was made this way for performance reasons. It's better to walk over data that is placed sequentially...
@hongzhidao Let's first think about how we can make those `$arg_*`, `$http_*`, `$cookie_*` magic variables the most efficient way. And I suppose that the most significant efficiency we can achieve...
What do you think, does it make sense to you?