Like http://www.chilkatforum.com/questions/8498/failing-to-connect-through-http-proxy issue, I get the same problem. As the answers I know the new chilkat socket connect to a webproxy(my squid web proxy which don't support non-HTTP traffic) with username&password always using CONNECT methond.
It is noticed that if visiting the remote resource with https url(https://www.xxx.com), it works well, because CONNECT method is the first step in the stardard visiting https process. However, when I visit the http url(http://www.xxx.com) resources with proxy server, the CONNECT method still be used in the process. The web proxy assumes that because the CONNECT method is being used, it's a SSL/TLS connection for HTTP. It notices that your port is not 443 and rejects it.
In the old chilkat(9.3.2), socket works well. With fiddler helping, I found the difference(between 9.3.2 and 9.5.0.68) is the old socket connect to http url resource with proxy server never use the CONNECT method.
My question is: Is there a solution to solve this? In an other word, Is there a function to avoid socket connect always use CONNECT method. Many proxy server don't support non-HTTP traffic. And issues will happen when these proxy servers used. I need a convenient switch to control the CONNECT method in my work.
Thanks,looking forward your reply.