anchor.diff:  <%= partial '../opsguide/ssl_termin_lb_only_pcf' %>
   <% end %>
   
  -##<a id="lb_and_gorouter_term"></a>Terminating SSL/TLS at the Load Balancer and Gorouter
  +##<a id="lb_and_gorouter_term"></a>Terminating TLS at the Load Balancer and Gorouter
   
   In this configuration two TLS connections are established: one from the client to the load balancer, and another from the load balancer to the Gorouter. This configuration secures all traffic between the load balancer and the Gorouter.
   
  
positive.code:   </td>
    <td><b>Load Balancer only</b>
    </td>
    <td><a href="#lb_term">Terminating SSL/TLS at the Load Balancer Only</a>
    </td>
  </tr>
  <%=vars.ssl_haproxy%>
  
negative.code: 
  To secure non-HTTP traffic over TCP Routing, terminate TLS at your load balancer or at the application. See [TCP Routing](enabling-tcp-routing.html) for details.
  
  ##<a id="ssl_options"></a>TLS Termination Options for HTTP Routing
  
  There are several options for terminating TLS for HTTP traffic. You can terminate TLS at the Gorouter, your load balancer, or at both. 
  
  The following table summarizes TLS termination options and which option to choose for your deployment.
  
  <table border="1" class="nice">
  <tr>
    <th>If the following applies to you:</th>
    <th>Then configure TLS termination at:</th>
    <th>Related topic and configuration procedure</th>
  </tr>
  <tr>
  