Greetings!
I'm reading the "TS Administration Guide: Release 5.5.2L" for UNIX.
It has a "Redirecting NSAPI HTTPS Requests" section on page 59. Starting with version 5, TS can handle HTTPS requests itself, can't it?
How does this directive in iw.cfg come into play:
[nsapi]
redirect_https_to_http=yes
The text below also mentions "secure server’s NSAPI plugin." Where did that plugin come from? Is it there by default?
Thanks : ),
S.
------------------------
Redirecting NSAPI HTTPS Requests
You can configure TeamSite to redirect HTTPS requests from TeamSite so they are served
from the Web daemon () over HTTP. To do this, your system must contain two Web servers:
• A secure NES or iPlanet Web server set up to process HTTPS requests.
• A non-secure server of any type that processes TeamSite web daemon HTTP requests.
To redirect HTTPS requests, set the following directive in the [nsapi ] section of your iw.cfg file:
redirect_https_to_http=yes
When redirection is enabled, all HTTPS requests originating from the browser and received
by the secure server’s NSAPI plugin are redirected to the web daemon. The web daemon
then sends the requests to the non-secure TeamSite server just as it would any request
originating from the browser. For example, if the NSAPI plugin on the secure server receives
an HTTPS request for a file in a TeamSite area such as:
https://teamsite_host /iw-mount/branch1/STAGING/bio.html
where teamsite_host specifies the host name (such as
www.example.com ), then the
request is redirected to the web daemon as follows:
http://teamsite_host :iwwebd_port /iw-mount/branch1/STAGING/bio.html
where iwwebd_port specifies the port number.
During the redirection process, some browsers will display a message warning that the
request is being sent to an insecure document. This is normal browser behavior. If you
see such a message, click OK to proceed. Note that HTTPS requests redirected to the web
daemon no longer have HTTPS security.
