TCP and SSL proxy junctions
We can create WebSEAL junctions that allow communication to traverse network topologies that use HTTP or HTTPS proxy servers. The create command requires one of the following arguments:
- -t tcpproxy
- -t sslproxy
Both create and add commands require the following options and arguments to identify the proxy server and the target Web server:
| Options | Description |
|---|---|
| -H host-name | The DNS host name or IP address of the proxy server. |
| -P port | The TCP port of the proxy server. |
| -h host-name | The DNS host name or IP address of the target Web server. |
| -p port | The TCP port of target Web server. Default is 80 for TCP junctions; 443 for SSL junctions. |
Example TCP proxy junction:
- pdadmin> server task web1-webseald-cruz create -t tcpproxy -H clipper -P 8081 -h www.ibm.com -p 80 /ibm
Example SSL proxy junction:
- pdadmin> server task web1-webseald-cruz create-t sslproxy -H clipper -P 8081 -h www.ibm.com -p 443 /ibm
TCP and SSL proxy virtual host junctions are also supported.
Parent topic: Advanced junction configuration
Related concepts
- Mutually authenticated SSL junctions
- WebSEAL-to-WebSEAL junctions over SSL
- Stateful junctions
- Use of /pkmslogout with virtual host junctions
- Junction throttling
- Management of cookies
- Passing of session cookies to junctioned portal servers
- Support for URLs as not case-sensitive
- Junctions to Windows file systems
- Standard junctions to virtual hosts
- UTF-8 encoding for HTTP header data
- WebSockets
Related tasks