@echo off
echo ========================================
echo MITM Proxy Debug Script
echo ========================================
echo.
echo This script will help diagnose why HTTPS CONNECT requests
echo are not reaching the proxy server.
echo.
pause

echo 1. Checking current Windows proxy settings...
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyEnable
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyServer
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyOverride
echo.

echo 2. Checking WinHTTP proxy settings...
netsh winhttp show proxy
echo.

echo 3. Testing if proxy port is listening...
netstat -an | findstr ":8080"
echo.

echo 4. Testing direct connection to proxy...
curl -v --max-time 5 http://127.0.0.1:8080/proxy-health
echo.

echo 5. Testing HTTP proxy functionality...
curl -v --proxy http://127.0.0.1:8080 --max-time 10 http://httpbin.org/ip
echo.

echo 6. Testing HTTPS with explicit CONNECT...
echo Sending manual CONNECT request...
(
echo CONNECT httpbin.org:443 HTTP/1.1
echo Host: httpbin.org:443
echo.
) | telnet 127.0.0.1 8080
echo.

echo 7. Testing HTTPS proxy with curl...
curl -v --proxy http://127.0.0.1:8080 --max-time 15 https://httpbin.org/ip
echo.

echo 8. Checking for conflicting proxy software...
tasklist | findstr /i "fiddler\|charles\|burp\|owasp"
echo.

echo 9. Testing with different curl proxy syntax...
curl -v -x 127.0.0.1:8080 --max-time 15 https://httpbin.org/ip
echo.

echo Debug complete. 
echo.
echo IMPORTANT: Check the MITM proxy console output during these tests.
echo If you see NO CONNECT requests in the proxy logs, the issue is 
echo with Windows proxy configuration or browser proxy detection.
echo.
pause