Progress® Telerik® Fiddler™ Classic Feedback Portal
Back to Feed
Request a Feature Report a Bug
Under Review
Last Updated: 03 Jan 2018 13:15 by Imported User
Imported User
Created on: 03 Jan 2018 05:59
Type: Feature Request
1
Not failing https requests in case of non-availability of network
Fiddler does not forward https requests if there is no network connection. Network i meant verified laptop by not connecting to any LANs but there were available wifi hotspots. This is value add as it would make fiddler more suspicious if it does not attempt to forward https requests. http requests are forwarded in same configuration.
1 comment
Eric
Posted on: 03 Jan 2018 06:00 
Can you please explain more specifically what you mean? It's not clear what you mean by "more suspicious."

When a client connects to a HTTPS proxy, it sends a HTTP request with the CONNECT method. The proxy will then attempt to establish a TCP/IP connection to the target site. If the connection is successful, the proxy will return "HTTP/1.1 200 Connection Established" to the client, which will then begin negotiation of a HTTPS connection through the tunnel. If the TCP/IP connection fails (e.g. because there's no network or the site is unreachable) the proxy will return a HTTP/502 or similar error to the client.

If you want Fiddler to return a "HTTP/1.1 200 Connection Established" for all CONNECT attempts, regardless of connectivity, you can use the AutoResponder with a rule like

method:CONNECT  *ReplyWithTunnel

(See https://groups.google.com/forum/#!topic/httpfiddler/UsS_r8EnTCI)
Create an account Log In
View
Type
Status