Originally posted by: Ali Naqi
Add WSAStartup(..) to ur code before running this.. it fails..
ReplyOriginally posted by: gzbugkiller
Great!
oh,my code
ReplyOriginally posted by: Cale Yao
Your article provides a simple way to process connect-oriented stream communication through proxy server.
If only there was a way for datagram-oriented communication. Is it necessary to have sock4/5 included ?
Thank you.
ReplyOriginally posted by: Alex
You mentioned DNS.H in the article, but it's not in the ZIP-file. I was just curious what the DNS.H file contains :-)
ReplyOriginally posted by: Ralf
Hi,
our proxy only accepts connection requests to port 443.
It's an Netscape-Proxy/3.5 Version.
To my understanding, in this case I need some process on the remote site which accepts this connection on 443 and establishes a connection for, say port 25 on the local or some other remote host.
This is some kind of "VPN" then, right ?
---------------------------------------------
Beside this issue, I have problems connectiog the proxy using your code at all. At first it doesn't find the IP-Adress if I configure the hostname in Client.SetProxySettings. If I use the IP-Adresses I get one step further, until :
bRet = connect(m_hSocket,(SOCKADDR*)&sockAddr, sizeof(sockAddr));
in SocketEx.h
It always returns -1 and WSAgetLastError tells me, WSAStartup has to be called before....
What I'am doing wrong ?
Thanks for help
Ralf.
Reply
Originally posted by: john
Hi,
I find your article very usefull, can you post some link to a few documentation/rfc/tutorial on https and proxy protocol?
Reply