<?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 Re: TCP Flow and Persistent SSL connection in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/tcp-flow-and-persistent-ssl-connection/m-p/168861#M2099</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Victor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;that's a browser issue.&lt;/P&gt;&lt;P&gt;If the browser decides to open mutliple connections, there is nothing we can do at the server level or CSS level.&lt;/P&gt;&lt;P&gt;Make sure your browser is setup to use HTTP/1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jun 2003 09:36:43 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2003-06-19T09:36:43Z</dc:date>
    <item>
      <title>TCP Flow and Persistent SSL connection</title>
      <link>https://community.cisco.com/t5/application-networking/tcp-flow-and-persistent-ssl-connection/m-p/168860#M2098</link>
      <description>&lt;P&gt;Here is our scenario.....apache web server --- CSS11506-----user&lt;/P&gt;&lt;P&gt;The 11506 is acting as a transparent proxy with SSL accel&lt;/P&gt;&lt;P&gt;for each TCP flow from the user....the CSS does TCP handshake, SSL negiotiation, data transfer, tear down......&lt;/P&gt;&lt;P&gt;The web page is made up of many tiny gif images...thus for each gif, there is an inordinate amount of overhead with the session setup and teardown.  This problem is alleviated by turning keepalives on for the apache web server, but this causes 404 errors on the user browser.&lt;/P&gt;&lt;P&gt;Is there a way to maintain a session persistence for the entire transaction, and not each individual TCP flow?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;&lt;P&gt;Victor&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jun 2003 12:49:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tcp-flow-and-persistent-ssl-connection/m-p/168860#M2098</guid>
      <dc:creator>vkasacavage</dc:creator>
      <dc:date>2003-06-17T12:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Flow and Persistent SSL connection</title>
      <link>https://community.cisco.com/t5/application-networking/tcp-flow-and-persistent-ssl-connection/m-p/168861#M2099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Victor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;that's a browser issue.&lt;/P&gt;&lt;P&gt;If the browser decides to open mutliple connections, there is nothing we can do at the server level or CSS level.&lt;/P&gt;&lt;P&gt;Make sure your browser is setup to use HTTP/1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2003 09:36:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tcp-flow-and-persistent-ssl-connection/m-p/168861#M2099</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-06-19T09:36:43Z</dc:date>
    </item>
  </channel>
</rss>

