WebTrac Configuration behind Spoofing SSL (Load Balancer)
RecTrac 3.1.10.12.00
Table of Contents
Problem
The set up of "Spoofing" the SSL to a Web Server through a Load Balancer causes the customer using the Load Balancer's SSL to spoof HTTPS to the Web Server (WebTrac) while IIS is only HTTP binding with no SSL Certificate loaded on it. Customers sometimes do this to maintain their SSL in one area, the load balancer, so that it can be used for multiple web servers without having to load it on each one.
However, to avoid 502 errors, through our Interface Parameters, we require an exact match of the URL to pass to RecTrac. Since the WebTrac server is handing off as HTTP through its bindings to the RecTrac server, it creates a mismatch back to the HTTPS parameters in RecTrac.
Error Message
502 Error on WebTrac
Solution
You will still create a WebTrac Interface Parameter using the HTTPS URL used for their WebTrac site in DB_utilities. Then go to Config.ini under <x>:\VSI3\RecTrac\Programs and edit it: Copy the URL entry made for WebTrac and immediately duplicate it under the original "HTTPS" URL, but adjust the copy URL as "HTTP" instead.
This will "trick" RecTrac into accepting the Web connection in config.ini to avoid the mismatch issue and thus the 502 error. Once accepted WebTrac will use the HTTPS as defined in RecTrac Interface Parameters.
Steps For Solution
- Use DB_Utilities and Update Interface Parameters to create the WebTrac Parameter with the valid URL (HTTPS).
- Go to Config.ini under <x>:\VSI3\RecTrac\Programs and edit it.
- Copy the URL entry made for WebTrac and immediately duplicate it under the original HTTPS URL.
- Adjust the copy URL to "HTTP."
- Navigate back to OpenEdge Explorer
- Restart WebLive Webspeed broker.