使用Python requests通过VPN访问公司内网服务器报502 Bad Gateway错误

Alright, let's dig into this 502 Bad Gateway error you're facing. Since your code works fine on the physical office network but breaks over VPN with proxy environment variables set, the issue almost certainly lies in how requests interacts with your proxy/VPN setup. Here are some actionable steps to troubleshoot and fix it:

1. Verify Your Proxy Environment Variables #

First, double-check that your HTTP_PROXY and HTTPS_PROXY variables are formatted correctly:

• They must include the full protocol prefix (e.g., http:// or https://) and correct port number, like HTTP_PROXY=http://proxy.yourcompany.com:8080
• Typos here are super common—make sure the proxy address matches what your IT team provided.
• Windows environment variables might not update immediately in running terminals/IDEs. Restart your Python environment (VS Code, command prompt, etc.) after setting them to ensure they're picked up.

2. Manually Specify Proxies in Requests #

Sometimes requests doesn't reliably read proxy settings from environment variables (especially on Windows). Bypass that by explicitly passing a proxy dictionary to your requests calls:

import requests

# Replace with your actual proxy details
proxies = {
    "http": "http://proxy.yourcompany.com:8080",
    "https": "http://proxy.yourcompany.com:8080"  # Most corporate HTTPS traffic uses the HTTP proxy
}

# If your proxy requires authentication, add your credentials:
# proxies = {
#     "http": "http://username:password@proxy.yourcompany.com:8080",
#     "https": "http://username:password@proxy.yourcompany.com:8080"
# }

response = requests.get("https://your-internal-server.yourcompany.com", proxies=proxies)
response.raise_for_status()  # This will show detailed error info if it fails

3. Test Connectivity Outside Python #

Rule out code issues entirely by testing with a tool like curl in your terminal:

curl -x http://proxy.yourcompany.com:8080 https://your-internal-server.yourcompany.com

If this also returns a 502, the problem isn't with Python—it's a VPN or proxy configuration issue. Reach out to your IT team to confirm:

• Your VPN connection is properly routing traffic to the internal network
• The proxy allows traffic from your VPN-assigned IP address
• The internal server is reachable over VPN

4. Check for Proxy Overrides in Your Code #

Make sure nothing in your code is overriding proxy settings. For example, if you're using a requests.Session, check if you've accidentally cleared the proxies:

session = requests.Session()
# Avoid this unless intentional: session.proxies = {}

# To see what proxies requests is actually using, run this:
print(requests.utils.get_environ_proxies("https://your-internal-server.yourcompany.com"))

This will print the proxy requests is trying to use—if it's empty or doesn't match your environment variables, that's the issue.

5. Handle Windows-Specific Proxy Quirks #

• PAC Scripts: If your company uses an automatic proxy configuration (PAC) script, requests can't parse it automatically. You'll need to extract the actual proxy address from the PAC file (ask your IT team for this) and use it in your proxies dictionary.
• Certificate Issues: Some corporate proxies intercept HTTPS traffic with a self-signed certificate. If you get a certificate error along with the 502, you can temporarily test with verify=False (not recommended for production):

  response = requests.get("https://your-internal-server.yourcompany.com", proxies=proxies, verify=False)
  

  For a permanent fix, configure verify to point to your company's root certificate file:

  response = requests.get("https://your-internal-server.yourcompany.com", proxies=proxies, verify="path/to/company-root-cert.pem")
  

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