Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Server Name Indication for outbound web services

Server Name Indication for outbound web services

Outbound HTTP requests, including outbound SOAP, REST, and GlideHTTPClient requests support Server Name Indication.

Server Name Indication (SNI) is a TLS extension that enables service providers to serve multiple host names from a single IP address. With SNI support, outbound web service requests specify the hostname to connect to as part of the TLS handshake. This information allows the server to present the correct certificate to the client.

SNI support is provided for outbound requests sent directly from an instance, as well as outbound requests sent through a MID Server. The hostname is automatically included in the HTTP request when SNI is enabled, it is not necessary to configure the request for SNI support.

For example, when SNI support is enabled, a REST message sent to the endpoint https://myhost.com/some/path will include the domain myhost.com in the TLS SNI extension.

The following podcast offers additional information on web services.

Configure Server Name Indication

Server Name Indication support is disabled by default for all outbound HTTP requests.

To enable or disable SNI support for outbound HTTP requests sent directly from the instance, set the system property glide.outbound.tls_sni.enabled to true or false (default).

To enable or disable SNI support for outbound HTTP requests sent through a MID Server, create the property glide.outbound.tls_sni.enabled on the MID Server with a value of true or false (default), then restart the MID Server.

Note: After you change the property, wait at least 30 seconds before testing a request to ensure that a cached connection is not reused.