• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            elva

            HTTP Tunneling

            Introduction

            HTTP Tunneling

            HTTP is a text-based protocol to retrieve Web pages through a Web browser. Mostly, if you are on a LAN connection, you are behind a proxy server; this proxy server has one HTTP proxy running on some defined port. In your Internet Explorer's Connection option, you specify LAN settings as required. This proxy server is definitely running on a text-based protocol, and you can only get HTTP-related data from the outside network, right!! Well, there is a small loophole from which you can go through HTTP and connect to the outside world and get any data you want in binary protocol, or even your own protocol. It's through HTTPS.

            HTTPS Explanation

            In HTTPS, data is transferred from browser to server and server to browser in a secure manner. It's a binary protocol; when it goes through a proxy, the proxy doesn't understand anything. The proxy just allows a binary stream to open and lets both server and client exchange the data. Now, we can fool the proxy server and connect to any server and exchange data. The proxy server will think that we are doing some secure HTTP session.

            For HTTPS, your browser connects to a proxy server and sends a command:

            CONNECT neurospeech.com:443 HTTP/1.0 <CR><LF>
            HOST neurospeech.com:443<CR><LF>
            [... other HTTP header lines ending with <CR><LF> if required]>
            <CR><LF>    // Last Empty Line

            Then, the proxy server treats this as some HTTP Secure Session, and opens a binary stream to the required server and port as defined. If a connection is established, the proxy server returns the following response:

            HTTP/1.0 200 Connection Established<CR><LF>
            [.... other HTTP header lines ending with <CR><LF>..
            ignore all of them]
            <CR><LF>    // Last Empty Line

            Now, the browser is connected to the end server and can exchange data in both a binary and secure form.

            How to Do This

            Now, it's your program's turn to fool the proxy server and behave as Internet Explorer behaves for Secure HTTP.

            1. Connect to Proxy Server first.
            2. Issue CONNECT Host:Port HTTP/1.1<CR><LF>.
            3. Issue <CR><LF>.
            4. Wait for a line of response. If it contains HTTP/1.X 200, the connection is successful.
            5. Read further lines of response until you receive an empty line.
            6. Now, you are connected to the outside world through a proxy. Do any data exchange you want.

            Sample Source Code

            Collapse
              // You need to connect to mail.yahoo.com on port 25
            // Through a proxy on 192.0.1.1, on HTTP Proxy 4480
            // CSocketClient is Socket wrapping class
            // When you apply operator << on CString, it writes CString
            // To Socket ending with CRLF
            // When you apply operator >> on CString, it receives
            // a Line of response from socket until CRLF
            try
            {
            CString Request,Response;
            CSocketClient Client;
            Client.ConnectTo("192.0.1.1",4480);
            // Issue CONNECT Command
            Request = "CONNECT mail.yahoo.com:25 HTTP/1.0";
            Client<<Request;
            // Issue empty line
            Request = "";
            Client<<Request;
            // Receive Response From Server
            Client>>Response;
            // Ignore HTTP Version
            int n = Response.Find(' ');
            Response = Response.Mid(n+1);
            // Http Response Must be 200 only
            if(Response.Left(3)!="200")
            {
            // Connection refused from HTTP Proxy Server
            AfxMessageBox(Response);
            }
            // Read Response Lines until you receive an empty line.
            do
            {
            Client>>Response;
            if (Response.IsEmpty())
            break;
            }while (true);
            // Coooooooool.... Now connected to mail.yahoo.com:25
            // Do further SMTP Protocol here..
            }
            catch (CSocketException * pE)
            {
            pE->ReportError();
            }

            Library Source Code

            The Dns.h file contains all DNS-related source code. It uses other libraries, as SocketEx.h, SocketClient.h, and NeuroBuffer.h.

            CSocketEx

            Socket functions as a wrapper class. (CSocket is very heavy and unreliable if you don't have the exact idea of how it works.) All the functions are of the same name as CSocket. You can use this class directly.

            CSocketClient

            Derived from CSocketEx and throws proper exceptions with details of Winsock errors. It defines two operators, >> and <<, for easy sending and receiving; it also changes network to host and host to network order of bytes if required.

            CHttpProxySocketClient

            Derived from CSocketClient, you can call the SetProxySettings(ProxyServer,Port) method and set proxy settings. Then, you can connect to the desired host and port as you need. The ConnectTo method is overridden, and it automatically implements an HTTP proxy protocol and gives you a connection without any hassle.

            How to Use CHttpProxySocketClient

            Collapse
              // e.g. You need to connect to mail.yahoo.com on port 25
            // Through a proxy on 192.0.1.1, on HTTP Proxy 4480
            // CSocketClient is Socket wrapping class
            // When you apply operator << on CString, it writes CString
            // To Socket ending with CRLF
            // When you apply operator >> on CString, it receives
            // Line of response from socket until CRLF
            try
            {
            CHttpProxySocketClient Client;
            Client.SetProxySettings("192.0.1.1",1979);
            // Connect to server mail.yahoo.com on port 25
            Client.ConnectTo("mail.yahoo.com",25);
            // You now have access to mail.yahoo.com on port 25
            // If you do not call SetProxySettings, then
            // you are connected to mail.yahoo.com directly if
            // you have direct access, so always use
            // CHttpProxySocketClient and no need to do any
            // extra coding.
            }
            catch(CSocketException * pE) {
            pE->ReportError();
            }

            Note: I usually don't program in the form of .h and .cpp different files, because using them the next time somewhere else is a big problem because you must move both files here and there. So, I put all the code in my .h file only; I don't write to the .cpp file unless it's required. You need to copy only the SocketEx.h, SocketClient.h, and HttpProxySocket.h files into your project's directory, and add line:

            #include "HttpProxySocket.h"

            after your:

            #if !defined(.....

            and so forth code of your Visual Studio-generated file. If you put anything above this, you will get n number of errors.

             

            posted on 2007-05-06 16:51 葉子 閱讀(695) 評論(0)  編輯 收藏 引用 所屬分類: 網絡安全

            久久精品国产一区| 色欲av伊人久久大香线蕉影院| 久久国产精品久久精品国产| 国产伊人久久| 久久99久国产麻精品66| 51久久夜色精品国产| 久久亚洲AV成人无码软件| 77777亚洲午夜久久多喷| 久久中文精品无码中文字幕| 国产综合久久久久久鬼色| 亚洲国产小视频精品久久久三级| 久久99精品久久久久婷婷| 亚洲国产精品无码久久久久久曰 | 国産精品久久久久久久| 精品久久久久久久国产潘金莲| 久久夜色精品国产亚洲| 久久99热这里只有精品国产| 国产2021久久精品| 国产精品久久久久aaaa| 久久中文骚妇内射| 久久成人国产精品免费软件| 久久精品免费网站网| 色综合久久中文综合网| 国产精品无码久久久久久| 日产精品99久久久久久| 亚洲国产精品无码成人片久久| 久久人人爽人人爽人人片AV高清 | 东方aⅴ免费观看久久av | 久久99热精品| 色成年激情久久综合| 久久国产精品-久久精品| 99久久精品费精品国产一区二区| 看久久久久久a级毛片| 日韩人妻无码精品久久免费一| 久久人做人爽一区二区三区| 久久精品桃花综合| 99久久免费国产精品特黄| 久久这里都是精品| 久久久久久久久久久久久久| 亚洲av伊人久久综合密臀性色| 久久久久人妻一区精品性色av|