如何配置Selenium打开手动可访问但自动化时空白的HTTPS生产页面？

Absolutely—you can absolutely resolve this with targeted Selenium Chrome configurations, no need to rely on loading your full user profile (though that workaround works too). Let’s break down why this happens and walk through actionable fixes:

Why This Happens #

Your production HTTPS site is likely checking for signals that distinguish automated browsers from real user sessions. Common triggers include:

• Selenium’s default "clean" browser environment missing trusted certificates, saved cookies, or custom security settings from your regular Chrome profile
• Detection of Selenium-specific identifiers (like the navigator.webdriver flag)
• A generic/automated user-agent string that the site blocks

Step-by-Step Configurations to Fix the Problem #

1. Spoof a Real User-Agent #

Selenium’s default user-agent has telltale signs of automation. Replace it with a genuine Chrome user-agent string (you can find your current one via chrome://version/):

from selenium import webdriver
from selenium.webdriver.chrome.options import Options

chrome_options = Options()
# Replace with your actual Chrome version's user-agent
chrome_options.add_argument("user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36")

driver = webdriver.Chrome(options=chrome_options)

2. Bypass Automation Detection #

Many sites flag Selenium via the navigator.webdriver property. Hide this and disable automation-related switches:

# Add these to your ChromeOptions
chrome_options.add_argument("--disable-blink-features=AutomationControlled")
chrome_options.add_experimental_option("excludeSwitches", ["enable-automation"])
chrome_options.add_experimental_option('useAutomationExtension', False)

# After initializing the driver, override the webdriver property
driver.execute_script("Object.defineProperty(navigator, 'webdriver', {get: () => undefined})")

3. Trust Production Site Certificates #

If your regular profile has trusted the site’s SSL certificate (e.g., internal enterprise certs), tell Selenium to use system-wide certificate stores:

chrome_options.add_argument("--use-system-ssl-certificates")
# If you need to trust a specific cert file, add this (replace with your cert path)
# chrome_options.add_argument("--ssl-certificate-file=/path/to/your/site-cert.crt")

4. Import Necessary Cookies (If Site Requires Login) #

If your manual profile has active login cookies, export them (via Chrome DevTools > Application > Cookies) and import them into Selenium:

# First navigate to the site to set the domain context
driver.get("https://your-production-site.com")

# Add your exported cookies (adjust values to match your site's cookies)
cookies = [
    {"name": "auth_token", "value": "your-auth-token", "domain": ".your-production-site.com"},
    {"name": "session_id", "value": "your-session-id", "domain": ".your-production-site.com"}
]

for cookie in cookies:
    driver.add_cookie(cookie)

# Refresh to load the page with valid session cookies
driver.refresh()

5. Load a Partial User Profile (Lightweight Alternative) #

Instead of loading your full profile, you can load just the necessary components (like certificates or cookie stores) to avoid privacy risks or environment bloat:

# Replace with your Chrome user data directory path
# Windows example: C:\\Users\\YourUsername\\AppData\\Local\\Google\\Chrome\\User Data
# Mac example: ~/Library/Application Support/Google/Chrome/
chrome_options.add_argument("--user-data-dir=/path/to/chrome-user-data")
# Specify a profile directory (use "Default" for your main profile)
chrome_options.add_argument("--profile-directory=Default")

Final Notes #

Start with the automation detection bypass and user-agent spoof—these fix the majority of such issues. If the problem persists, check if the site relies on specific cookies or certificates, then apply the corresponding configuration.

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