Mixed Content Proxy Test

🌐 Current Page Security

⚠️ Mixed Content Policy

Browser Security Rule: HTTPS pages cannot make requests to HTTP endpoints

BLOCKED: HTTPS → HTTP (Subresources)
WARNING: HTTPS → HTTP (Navigation)
ALLOWED: HTTPS → HTTPS
ALLOWED: HTTP → HTTP

🧪 Mixed Content Tests

❌ Common Scenarios That Fail

# Page: https://example.com
# Proxy rule: api.service.com → http://my-proxy.local:8080
# Result: ❌ BLOCKED - Mixed content violation

✅ Working Solutions

Option 1: Use HTTPS for Proxy Target

# Proxy rule: api.service.com → https://my-proxy.com
# Result: ✅ WORKS - Both HTTPS

Option 2: Setup HTTPS on Local Proxy

# Use mkcert or similar to create local HTTPS
# Proxy rule: api.service.com → https://localhost:8443
# Result: ✅ WORKS - HTTPS to HTTPS

Option 3: Browser Flags (Development Only)

# Chrome: --disable-web-security --disable-features=VizDisplayCompositor
# Firefox: security.mixed_content.block_active_content = false
# Result: ⚠️ WORKS but INSECURE

🔧 Extension Capabilities

Request Type	HTTPS → HTTP	Extension Override
Main Frame Navigation	⚠️ Warning shown	✅ Can redirect
fetch() / XHR	❌ Blocked	❌ Still blocked
Images / CSS	❌ Blocked	❌ Still blocked
Scripts / Modules	❌ Blocked	❌ Still blocked

🔒 Mixed Content Proxy Test