Xiaochen Wang

think it resolved. feel free to reopen if u still have the same problem

> When I go to http, X-Forwarded-For is transmitted correctly, and when I use https it disappears. For https, the raw data is proxied by this module directly, and it...

think it resolved, if you still have any problem, feel free to reopen or file a new issue

It may be your local nginx environment. The configure error tells you that it cannot check the size of sig_atomic_t (maybe 4, 8, 16 bytes) in ur environment.

think it resolved. feel free to reopen if u still have the same problem

See this https://github.com/chobits/ngx_http_proxy_connect_module/issues/42#issuecomment-502985437.

use curl `-x` option for HTTPS tunnel. The request of your curl is handled by original nginx module(HTTPS module), not by this module(proxy_connect module).

> but i find i could not catch the https request. Yeah, this is in line with expectations. For CONNECT tunnel protocol, the proxy server ( this module ) cannot...

think it resolved. feel free to reopen if u still have the same problem

If you wanna to self-control upstream ip address, you can use [$proxy_connect_address directive](https://github.com/chobits/ngx_http_proxy_connect_module#proxy_connect_address). The controlling logic can be implemented via lua or nginx configuration. This test case( via lua) may...