mirror of
https://github.com/3proxy/3proxy.git
synced 2026-09-02 12:55:49 +08:00
488317da1d
httpsrv parsed Content-Length and never read what followed. The reply is followed by a close, and closing a socket that still holds unread data resets the connection instead of ending it, so a POST could cost the client the reply it was about to read. Windows does that reliably; the same test passes on Linux and macOS, which is why it looked flaky. Drain the body, bounded at a megabyte. The test CA was built with -addext, which LibreSSL - the openssl on a stock macOS - does not apply the same way, leaving a certificate that is not usable as a CA and a client that cannot build a chain to it. Put the extensions in a file both accept, and verify the generated chain before any of it is handed to a proxy, so a failure there is not read as a fault in the proxy. |
||
|---|---|---|
| .. | ||
| admin.py | ||
| httpsrv_auth.py | ||
| httpsrv_ops.py | ||
| httpsrv_parsing.py | ||
| httpsrv_rules.py | ||
| parent_ports.py | ||
| proxy_http.py | ||
| socks.py | ||
| ssl.py | ||