Xiaochen Wang

new version has been released with this issue resolved

Hi all, the issue `400 bad request replied from your nginx` means that this module is not installed into your nginx binary. If you compile a standalone nginx with right...

Issue locked and closed. If you still have the similar problem, please file a `new` issue.

Your original nginx binary file should be replaced by new nginx binary compiled with 1018 patch. If your nginx binary compiled without 1018 patch, it will not handle CONNECT request....

I give a complete solution to 400 bad request issue, you can check it on :https://github.com/chobits/ngx_http_proxy_connect_module/issues/136#issuecomment-1264290051

Hi @scutkim We know that tunnel proxying has two direction: upstream and downstream. For upstream, this module provides `proxy_connect_{read|send|connect}_timeout` to control timeout between nginx and upstream. For downstream, this module...

For nginx 1.20.1, you can use proxy_connect_rewrite_1018.patch. The patch proxy_connect_rewrite_102101.patch file you used is for nginx 1.21.1+

@jamiepmullan Currently not in plan. Hope that I can have free time to complete it or Someone can pull a reqeust for this issue. Details are in first comment.

This is technically feasible. But this module does not support this feature. It needs a new nginx upstream module to fire CONNECT tunnel request to upstream and then proxy data...

hi @notariuss Can you post ur rej file:`src/http/ngx_http_request.c.rej`, let me check it . I cannot reproduce this issue from `nginx-1.19.2` and proxy_connect_rewrite_1018.patch ``` WINDOWS-V0HQ9PG nginx-1.19.2 $ pwd /home/xiaochen/pc/nginx-1.19.2 WINDOWS-V0HQ9PG nginx-1.19.2...