`499` happens on `nginx` when the client closes the connection before `nginx` replies. See: https://stackoverflow.com/questions/12973304/possible-reason-for-nginx-499-error-codes

The solution is to close the connection after the response is received from the server.

…p-get-causing-nginx-to-fail-with-499

Fix (python): Fix miniclient.http_get() causing nginx to fail with `499`

…o-support-chunked-responses

Fix (python): Fix http library to support chunked responses

…response body if `Content-Length` or `Transfer-Encoding` HTTP Headers are absent

This fixes a critical regression that causes the BF2 server to not process stats if the ASP webserver does not respond with `Content-Length` or `Transfer-Encoding` HTTP Headers.

Fixes regression in #2.

…miniclient.http-get-to-read-full-response-body-if-content-length-or-transfer-encoding-http-headers-are-absent

Fix (python): Fix regression in `miniclient.http_get()` to read full response body if `Content-Length` or `Transfer-Encoding` HTTP Headers are absent

Feature (ci): Add github workflows

…el-to-release-drafter.yml

Enhancement (ci): Add `change` label to `release-drafter.yml`

…files-to-asp

Docs: Add notice about moving files to ASP