<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

 
 
  <channel>
    <title>Server Name Indication on ServiceNow Developer Blog</title>
    <link>https://developer.servicenow.com/blog.do?p=/tags/server-name-indication/</link>
    <description>Recent content in Server Name Indication on ServiceNow Developer Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 21 Sep 2017 20:08:02 +0000</lastBuildDate>
    
        
        
         
        <atom:link href="https://developer.servicenow.com/blog.do?p=/tags/server-name-indication/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Enabling SNI (Server Name Indication) in your Jakarta Instance</title>
      <link>https://developer.servicenow.com/blog.do?p=/post/enabling-sni-server-name-indication-in-your-jakarta-instance/</link>
      <pubDate>Thu, 21 Sep 2017 20:08:02 +0000</pubDate>
      
      <guid>https://developer.servicenow.com/blog.do?p=/post/enabling-sni-server-name-indication-in-your-jakarta-instance/</guid>
      <description>I&amp;rsquo;ll start with the good stuff. Starting with Jakarta, SNI is supported! If you need to enable it, create a system property named glide.outbound.tls_sni.enabled and set the value to true. After you set this property, it make take up to 30 seconds for the change to take effect. If you&amp;rsquo;re using a MID server, create a MID server property with the same name and restart the MID Server.
If you don&amp;rsquo;t know what SNI is, don&amp;rsquo;t worry, you&amp;rsquo;re not alone.</description>
    </item>
    
  </channel>
</rss>