Last updated on FEBRUARY 11, 2017
Applies to:Web Cache - Version 10.1.2.0.2 to 18.104.22.168.0 [Release AS10gR2 to Oracle11g]
Information in this document applies to any platform.
***Checked for relevance on 16-Aug-2015***
The objective to have the following Webcache architechture in place:
- Browser http://www.abc.com/ - http 80 - external LB - http 80 - Webcache - http 80 - intenal LB
- Browser https://www.abc.com - https 443 - SSL accelerator/external LB - http 443 - Webcache - http 443 - internal LB
The Webcache config is as follows:
- Host Name: www.abc.com, port 80
- Host Name: www.abc.com, port 443
- Server Type: Web Application, Host Name: wwwabccom-wp-p1.gen.local, Port: 80
- Server Type: Web Application, Host Name: wwwabccom-wp-p1.gen.local, Port: 443
1. Site Pattern: www.abc.com:80 , Origin Server: wwwabccom-wp-p1.gen.local:80
2. Site Pattern: www.abc.com:443 , Origin Server: wwwabccom-wp-p1.gen.local:443
The Load Balancer terminates SSL and forwards traffic as HTTP over port 443 to the webcache, but this does not have 443 in the URL.
Webcache handles this traffic as if it was send as HTTP over port 80 and routes all traffic to wwwabccom-wp-p1.gen.local:80
After terminating SSL at a layer other than Web Cache (for example, a hardware load balancer or router appliance that has a SSL acceleration card), Web Cache needs to be able to accept HTTP traffic.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms