CHAPTER16 Services
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
â– The NGINX directive for this parameter is "proxy_bind".
'Additional Directive
Set'
directive-set
[HTTPLocation_
AdditionalDirectiveSet]
Assigns an NGINX directive set for the HTTP location. To configure
NGINX directives, see Configuring HTTP Directive Sets on
page272.
'Cache'
cache
[HTTPLocation_
Cache]
Enables the caching of files in this location.
â– [0] No
â– [1] Yes (default)
Note:
â– Currently, this feature is not supported.
â– The NGINX directive for this parameter is "proxy_cache
zone|off".
SSL
'TLS Context'
tls-context
[HTTPLocation_
TLSContext]
Assigns a TLS Context for the TLS connection with the HTTP
location.
To configure TLS Contexts, see Configuring TLS Certificate
Contexts.
Note:
â– The parameter is applicable only if the connection protocol is
HTTPS (configured in the 'Upstream Scheme' parameter,
above).
â– The NGINX directives for this parameter are "proxy_ssl_
certificate", "proxy_ssl_certificate_key", "proxy_ssl_ciphers",
"proxy_ssl_protocols", and "proxy_ssl_password_file".
'Verify Certificate'
verify-cert
[HTTPLocation_
VerifyCertificate]
Enables TLS certificate verification when the connection with the
location is based on HTTPS. It verifies the certificate of the
incoming connection request from the Upstream Group.
â– [0] No = (Default) No certificate verification is done.
â– [1] Yes = The device verifies the authentication of the certificate
received from the HTTPS location. The device authenticates the
certificate against the trusted root certificate store associated
with the assigned TLS Context (see 'TLS Context' parameter
above) and if ok, allows communication with the HTTPS
location. If authentication fails, the device denies communication
(i.e., handshake fails). The device can also authenticate the
certificate by querying with an Online Certificate Status Protocol
(OCSP) server whether the certificate has been revoked. This is
also configured for the associated TLS Context.
Note:
â– The parameter is applicable only if the connection protocol is
HTTPS (configured in the 'Upstream Scheme' parameter,
above).
â– The NGINX directive for this parameter is "proxy_ssl_verify".
- 265 -