Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Sorry for the poor title, but basically what I am trying to achieve is have an application that will use a TCPListener to wait for incoming connections and then forward those to their intended destination. Forwarding regular Http requests is easy enough, but what steps do I need to take in order to “proxy” an HTTPS connection?
You can’t read the content of HTTPS communications without being either the source or the destination. Nobody in the middle can eavesdrop. So, unless you know the destination before-hand (say, if someone manages to send you the target IP out-of-band), you’re stuck.
NITPICK EDIT: That’s not entirely true. You could pretend to be the destination and interfere with the handshaking process. You will be able to see the content of the request, but the user will see an incorrect-certificate warning.