Unable to use SSL with software-based or name-based (non-IP address based) virtual hosts?
 Technote (FAQ)
 
Question
Why am I unable to configure WebSphere® Edge Server to use SSL with software-based or name-based (Non-IP Address based) Virtual Hosts?
 
Cause
The Transmission Control Protocol (TCP) controls the transport of data between networked computers. Protocols such as HTTP run on top of TCP in the sense that they all use TCP to support application tasks.

SSL runs above the TCP layer but below the Application layer, encapsulating Application layer protocols like HTTP. When an SSL connection is established, the server must negotiate the SSL protocol parameters (correct cipher suite, and so forth) with the client. This is known as an SSL Handshake.

The HTTP Host request header has to be read for the correct software-based or named-based virtual server to be launched . This is not possible until the SSL Handshake completes; however, this data is needed at the SSL Handshake phase.

 
Answer
WebSphere Edge Server supports using the IP address to enable SSL.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Edge Server Caching Proxy AIX, HP-UX, Linux, Linux Red Hat - pSeries, Linux Red Hat - zSeries, Solaris, Windows 6.1, 6.0, 5.1, 5.0
Application Servers Runtimes for Java Technology Java SDK
 
Product Alias/Synonym
WTE
Web Traffic Express
Caching Proxy
Proxy
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1031246
IBM Group: Software Group
Modified date: Jun 1, 2006