This gives me a webpage, but not the one I want. Then, for the HTTPS post request, I do a POST as normal, the only change being that i've 'https' in the uri rather than 'http'. What I've been doing so far is making a HttpWebRequest with method='CONNECT', and POSTDATA with just a value tbusername and tbpassword that I found on the webpage. NET CLR 2) Host: Content-Length: 379 Connection: Keep-Alive Cache-Control: no-cache Cookie: action= The response that comes back from this request is full of new cookies and that's where I want to get to. The next thing that fiddler shows up is a request for another page: Request: POST //lbr_portal HTTP/1.1 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/xaml+xml, application/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Referer: Accept-Language: en-ie Content-Type: application/x-Windows NT 5.1 SV1.

CN=VeriSign Class 3 Extended Validation SSL SGC CA, OU=Terms of use at (c)06, OU=VeriSign Trust Network, O='VeriSign, Inc.', C=US. Secure Protocol: Tls Cipher: TripleDes 168bits Hash Algorithm: Sha1 160bits Key Exchange: RsaSign 4096bits = Client Certificate = None. Secure traffic flows through this connection. NET CLR 2) Host: Content-Length: 0 Proxy-Connection: Keep-Alive Pragma: no-cache Response: HTTP/1.1 200 DecryptTunnel Established Timestamp: 14:49:22:3253 FiddlerGateway: Direct This is a HTTPS CONNECT Tunnel. In Fiddler, I can see the following: Request: CONNECT HTTP/1.0 User-Agent: Mozilla/4.0 (compatible MSIE 6.0 Windows NT 5.1 SV1. Before I reach the first HTTP CONNECT, it's all going fine. I'm using HttpWebRequests to navigate to the initial pages, collect VIEWSTATES and cookies etc. I'm using Fiddler to debug the website's behaviour. I've reached a deadend when it comes to HTTP Connects and HTTPS POSTS. I'm trying to login to a website using HttpWebRequests.

Fiddler vs wireshark vs firebug