TLS 1.2 Restriction in Node 18 Affects Proxy Configuration for HTTPS Backends #17765
Description
Bug report
What is the current behavior?
When utilizing Angular 15 and Node 18 in a local development environment, the proxy configuration in webpack fails to function as expected when targeting HTTPS backends using TLS 1.2. This issue arises from the TLS 1.2 restriction imposed by OpenSSL 3, which is used by Node 18. The restriction prevents connections to remote endpoints using TLS versions lower than 1.3 due to security concerns.
If the current behavior is a bug, please provide the steps to reproduce.
- Set up a local development environment with Angular 15 and Node 18.
- Configure the proxy settings in webpack to point to a backend using HTTPS with TLS 1.2.
- Attempt to access the backend via the proxy from the local development environment.
- Observe the failure in proxy configuration, preventing access to the backend due to TLS 1.2 restriction.
// Example of webpack proxy configuration
module.exports = {
//...
devServer: {
proxy: {
'/api': {
target: 'https://your-backend.com',
secure: false
}
}
}
};
What is the expected behavior?
The proxy configuration should function correctly, allowing the local development environment to communicate with the backend using TLS 1.2 without any issues. This functionality is crucial for a smooth development, testing, and debugging process, especially in environments where upgrading to TLS 1.3 is not immediately feasible.
Other relevant information:
webpack version: 5.89.0
Node.js version: 18.18.2
Operating System: Windows and Ubuntu (Linux)
Additional tools: Angular CLI