Previous versions of BlueCat Gateway let users directly edit Apache configuration files for Gateway's Apache host servers. As of version 21.11.2, Gateway will override those settings on startup. If you customized Apache server settings on your system, you must move those customized settings to either a Global Apache configuration file, and/or the HTTP/HTTPS configuration files.
You might also need to move SSL certification files to a new location. For more details, see Updating certificates and custom Apache configurations on legacy systems.
BlueCat Gateway makes use of two Apache virtual hosts, one for HTTP access and one for HTTPS access. Gateway automatically reconfigures Apache during startup; any settings made within the Apache server itself might be overridden.
You can't configure these Apache servers directly. Instead, you can configure settings used by these Apache hosts in the following locations:
||Within the BlueCat Gateway UI itself, using
Gateway settings. Changes made in Gateway automatically update the
standard JSON configuration file,
Important: Do not configure Apache settings within
|2||Global Apache configuration file||
|| Within a Global Apache Configuration file
|3||Server-specific configuration files||
|| Within the two HTTP/HTTPS Apache Configuration files
https.conf files are useful to configure settings not available
within the Gateway UI, such as ServerName and ServerAdmin.
email@example.com the Global Apache Configuration file (
global.conf), then set it to
- Gateway's HTTPS Apache server will use
firstname.lastname@example.org, inherited from the Global Apache Configuration file.
- Gateway's HTTP Apache server will use