Http node + proxy - got error

Nick_K_H · September 4, 2023, 11:55am

Found several related topics:

github.com/axios/axios

Add support for HTTPS over HTTP on Node.js

axios:v1.x ← ppati000:https-over-http

opened 06:10PM - 06 Oct 22 UTC

ppati000

+172 -28

So far, Axios did not support HTTPS requests over HTTP proxies. This pull req…uest implements of `CONNECT` requests to establish a tunnel through the proxy. The implementation works with both `Connection: close` and `Connection: keep-alive`, so that multiple HTTPS requests can be sent after one `CONNECT`. Only Node.js is supported for now. This pull request should fix the following issues, which still seem to be unresolved: * https://github.com/axios/axios/issues/4531 * https://github.com/axios/axios/issues/3384 Feedback is highly appreciated! ### Caveats If the upstream server closes the connection first (e.g., when keep-alive is disabled), the proxy may send an RST packet to the client. Here's what I believe is happening after some Wireshark debugging: 1. After sending the response, the upstream server sends TLS close_notify and FIN=1. 2. Proxy relays the packet to the client. 3. Proxy sends FIN reply to upstream server on its own (closing its connection with the upstream server) 4. Client sends TLS close_notify packet back to the proxy 5. Proxy does not understand TLS and has already closed the connection to the upstream server => sends RST to client. 6. Node.js triggers `ECONNRESET` although the HTTPS response has already been received (`res.complete === true`). My mitigation for this issue was to ignore `ECONNRESET` errors if `res.complete === true`. This mitigation does not work with `follow-redirects`, so redirect support is disabled for HTTPS over HTTP.