Rogue Wave banner
Previous fileTop of DocumentContentsIndex pageNext file
Secure Communication Module User's Guide
Rogue Wave web site:  Home Page  |  Main Documentation Page

8.2 Using the HTTP CONNECT Method with the HTTPS Package

The HTTP CONNECT method creates an end-to-end tunnel between two machines through a proxy/firewall machine.

The HTTP CONNECT method can be used only with the client class (in our case RWHttpsSecureSocketClient).

If you want to access secure content on a machine behind a proxy, your application must:

  1. Connect to the proxy insecurely.

    Normally, when using RWHttpsSecureSocketClient, the connection is secure from the time of connection. To start out as a nonsecure HTTP client so that the application can connect to the proxy, pass the enumeration RW_HTTPS_START_INSECURE as the second parameter to the static make() function of RWHttpsSecureSocketClient. At this point, the class behaves like class RWHttpSocketClient in the HTTP package.

    For more information about connecting to proxies, see the chapter on the HTTP protocol in the Internet Protocols Module User's Guide.

  2. Ask the proxy to create a tunnel to the secure machine.

    After step 1, your application can use standard HTTP commands to connect to the proxy and send the CONNECT request for a tunnel to the remote (secure) server.

  3. Direct the HTTPS package to begin using security. Do this by calling the secureUpgrade() member function on RWHttpsSecureSocketClient. The function returns true if a secure connection is established.

    After the CONNECT request returns from the proxy successfully, your channel to the secure server is established, as if you had connected to the server directly.

From this point on, you can use standard HTTP client commands to write your application.

Example 14: HTTPS CONNECT Example


Starts the HTTPS client insecurely (using a standard TCP/IP socket) by passing RW_HTTPS_START_INSECURE as the second parameter to make().


Creates the CONNECT request with the name of the "real" server (the server behind the proxy).


Connects our client to the proxy machine.


Submits our CONNECT request, which asks the proxy to set up a tunnel to the real machine.


If a successful (200 series) reply is returned from the server, the tunnel has been established.


Calls secureUpgrade() to start using SSL.


Constructs and submits our request to the actual server (behind the proxy).


Finally, on success, displays the page received from the server.

Previous fileTop of DocumentContentsNo linkNext file

Copyright © Rogue Wave Software, Inc. All Rights Reserved.

The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.