mabjmabj
May 15th, 2003, 04:42 AM
Hi all,
I have an application that uses SSL when it communicates with a web server. Everything works as expected until I add a proxy in between. My app sends a CONNECT to the proxy, receives a successful 200 back, and then tries to initiate the SSL handshake.
The problem starts when I send my Connect, some proxies (such as Microsoft ISA Server) sends a HTTP Continue message to the web server.
And when I send my client hello message to the server the web server, for some reason, dislikes this message, drops the entire TCP connection and terminates the SSL handshake process (which never really started).
Some other proxies will not send this HTTP Continue message to the web server when I send my Connect message and when I send my Client Hello message I will receive a Server Hello message and the communication works just fine.
Now, why do some HTTP proxies send these messages when others don't? What does this message mean, Is there anything I can do prevent this behaviour. Well it must be because a standard web browser such as MSIE or Netscape can establish a SSL communication to my Web server through Microsoft ISA Server.?
Thanks,
M-J
I have an application that uses SSL when it communicates with a web server. Everything works as expected until I add a proxy in between. My app sends a CONNECT to the proxy, receives a successful 200 back, and then tries to initiate the SSL handshake.
The problem starts when I send my Connect, some proxies (such as Microsoft ISA Server) sends a HTTP Continue message to the web server.
And when I send my client hello message to the server the web server, for some reason, dislikes this message, drops the entire TCP connection and terminates the SSL handshake process (which never really started).
Some other proxies will not send this HTTP Continue message to the web server when I send my Connect message and when I send my Client Hello message I will receive a Server Hello message and the communication works just fine.
Now, why do some HTTP proxies send these messages when others don't? What does this message mean, Is there anything I can do prevent this behaviour. Well it must be because a standard web browser such as MSIE or Netscape can establish a SSL communication to my Web server through Microsoft ISA Server.?
Thanks,
M-J