With RaidenHTTPD's HD-RW httpd rewritable redirection, you are able to easily redirect a http request to another web server. For example, with an IIS running on port 8080, the execution result will of course be delivered to the web browser via RaidenHTTPD and the client browser will think it is connecting to a single RaidenHTTPD while browsing inside a redirected web site. (similar to reverse proxy in apache mod_proxy module)

Scenario 1: While running RaidenHTTPD on port 80, you setup two extra virtual hosts of asp.xxx.com and jsp.xxx.com and redirect them to IIS and Tomcat web servers. You are able to integrate these two application servers into RaidenHTTPD.

Scenario 2: While running RaidenHTTPD on port 80 and redirecting other web server on another port, RaidenHTTPD is able to enhance the output of the other web server. For example, even though the other server does not support SSL/GZIP/Keep-Alive, you can still add these capabilities to it by using HD-RW to redirect the back-end server.

Scenario 3: With HD-RW, RaidenHTTPD is able to protect the intranet web server. For example, you can setup a real web server inside the LAN that is isolated by firewall while RaidenHTTPD is simultaneously accessing both the internet and the intranet and redirecting information back and forth in between.

Visitors connect to the path or virtual host that is pointing to another redirected location. EX: A server hosting 'www.yourhost.com' with RaidenHTTPD may request the /asp/ virtual path of 'http://www.yourhost.com/asp/' to be redirected to a IIS web server on port 8080.

RaidenHTTPD receives the request headers from web browser and carrys out some pre-processing for cookies,post data..etc. RaidenHTTPD prepares and modifies necessary information and then emulates itself as a web client before sending out the initial request to the target web server.

RaidenHTTPD redirects the client's request to the pre-defined back-end web server in the background. EX: RaidenHTTPD is sending requests from client to the pre-defined IIS or APACHE.

RaidenHTTPD is receiving the returned web page result from the pre-defined back-end web server. EX: RaidenHTTPD gets an ASP page from IIS.

RaidenHTTPD is managing the post-processes for the returned page from the pre-defined back-end server. RaidenHTTPD may compress and/or encrypt the resulting page using SSL before it sends it out to the client.

Final stage, RaidenHTTPD is sending the final result to the client. RaidenHTTPD sends out the processed resulting page to client's Internet Explorer.

Requirements:

RaidenHTTPD 1.1.31 or above with commercial license

How to setup:

Editing

RaidenAdmin->Configuration->VirtualHOST options tab->click on a virtual host->click on a virtual path (usually /)->right mouse click->edit

Enter our host syntax http://hostname:port/path/ in the disk path/URL input box.

http://hostname:80/path/ , http://127.0.0.1:8080/ , http://127.0.0.1/dir/



Adding a new one

 

Click on a virtual host->right mouse click->add virtual path



Please restart web server after the procedure is done.

 

Spec:

RaidenHTTPD HD-RW V1.0 - back-end Web Server communications
Keep-Alive	Supported
Compression	Supported *Keep-Alive is disabled when it's in use
HTTP POST	Supported
Chunked	Supported
Referer patch	Supported
HOST patch	Supported
HTTPS	Not Yet
RaidenHTTPD HD-RW V1.0 - web browser communications
Keep-Alive	Supported
Compression	Supported
HTTP POST	Supported
Chunked	Not necessary
HTTPS	Supported

Option HD-RW security option "Accept X-Forwarded-For from IP"

 

If your hd-rw backend server wishes to accept this http header from its frontend hd-rw server, please enter the frontend's IP address in this edit box, so the raidenhttpd can LOG correct IP addresses in the log file on the backend server.