<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problem with HTTPS/TLS and ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/problem-with-https-tls-and-asa/m-p/2116082#M395363</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Conifguration please.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is path through traffic right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please give details of the source network and destination network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Nov 2013 00:19:17 GMT</pubDate>
    <dc:creator>jumora</dc:creator>
    <dc:date>2013-11-14T00:19:17Z</dc:date>
    <item>
      <title>Problem with HTTPS/TLS and ASA</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-https-tls-and-asa/m-p/2116080#M395361</link>
      <description>&lt;P&gt;There is a site that we are trying to connect to that appears to only accept TLSv1.&amp;nbsp; When we try to connect from behind the ASA, it looks like TLS is not being permitted.&amp;nbsp; Based on a packet capture, it looks like the client is only trying SSL, which is then denied at the server because it's disabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try from outside the firewall, it works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What on the ASA could prevent a web client from trying to negotiate TLS?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:25:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-https-tls-and-asa/m-p/2116080#M395361</guid>
      <dc:creator>jason.williams</dc:creator>
      <dc:date>2019-03-12T00:25:45Z</dc:date>
    </item>
    <item>
      <title>Problem with HTTPS/TLS and ASA</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-https-tls-and-asa/m-p/2116081#M395362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jason,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you please help me if you got the issue resolved.. we are currently facing this issue &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Nov 2013 17:47:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-https-tls-and-asa/m-p/2116081#M395362</guid>
      <dc:creator>NDP</dc:creator>
      <dc:date>2013-11-13T17:47:27Z</dc:date>
    </item>
    <item>
      <title>Problem with HTTPS/TLS and ASA</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-https-tls-and-asa/m-p/2116082#M395363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Conifguration please.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is path through traffic right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please give details of the source network and destination network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Nov 2013 00:19:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-https-tls-and-asa/m-p/2116082#M395363</guid>
      <dc:creator>jumora</dc:creator>
      <dc:date>2013-11-14T00:19:17Z</dc:date>
    </item>
  </channel>
</rss>

