升级TLS版本前咨询：axios支持哪些TLS版本？

Hey there! Great question—since you're gearing up for a TLS version upgrade and relying on Axios for HTTP requests, let’s break down exactly how its TLS support works, and how you can ensure your requests stay smooth during the upgrade.

Key Background: Axios Doesn’t Handle TLS Directly #

First, it’s important to note that Axios itself doesn’t implement TLS support from scratch. Instead, it relies on the underlying environment’s network APIs:

• In Node.js: Axios uses Node.js’s built-in https module.
• In browsers: Axios uses either the XMLHttpRequest API or the modern Fetch API, depending on the browser and your Axios configuration.

This means the TLS versions Axios supports are entirely determined by the environment it’s running in.

TLS Support in Node.js Environments #

For Node.js, the TLS versions available depend on your installed Node.js version:

• Node.js 10.x and above: Supports TLS 1.0, 1.1, 1.2 (TLS 1.3 was added in Node.js 11.x, but became stable in 12.x).
• Node.js 12.x+: By default, enables TLS 1.2 and 1.3, while still allowing fallback to older versions if needed.
• Node.js 18.x+: Defaults to only enabling TLS 1.2 and 1.3, with TLS 1.0/1.1 disabled by default (you can re-enable them via configuration if absolutely necessary, though it’s not recommended for security).

Customizing TLS Versions in Node.js

If you want to enforce specific TLS versions (like requiring TLS 1.2 or higher), you can configure a custom httpsAgent in Axios:

const axios = require('axios');
const https = require('https');

// Create an agent that enforces TLS 1.2 or 1.3
const tlsAgent = new https.Agent({
  minVersion: 'TLSv1.2',
  maxVersion: 'TLSv1.3'
});

// Use this agent in your Axios requests
axios.get('https://your-target-api.com', {
  httpsAgent: tlsAgent
})
.then(response => console.log('Request successful!'))
.catch(error => console.error('Request failed:', error));

TLS Support in Browser Environments #

In browsers, Axios’s TLS support is tied to what the browser itself supports. All modern browsers (Chrome, Firefox, Safari, Edge) have supported TLS 1.2 since at least 2015, and most have supported TLS 1.3 since 2018-2019.

• Modern browsers disable TLS 1.0 and 1.1 by default for security reasons, so if your server is upgrading to drop those versions, your users on up-to-date browsers won’t face issues.
• You don’t need to configure anything special in Axios for browsers— the browser will automatically negotiate the highest supported TLS version with your server.

Quick Tips for a Smooth Upgrade #

1. Verify your environment: Check your Node.js version (run node -v) or audit your user’s browser distribution to ensure they support your target TLS versions.
2. Test before deploying: Send test requests with Axios to your server after the TLS upgrade to confirm no connection errors occur.
3. Prioritize security: Avoid re-enabling older TLS versions (1.0/1.1) unless absolutely necessary, as they have known vulnerabilities.

内容的提问来源于stack exchange，提问作者reintroducing