<?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 Reverse Proxy Cache Problem in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/reverse-proxy-cache-problem/m-p/294856#M4557</link>
    <description>&lt;P&gt;I am having problems with IE5.5 clients when reverse proxy caching is configured with a CSS.  The clients are using HTTPS, which is terminated on the CSS.  The CSS then communicates with the CE and the origin server using HTTP.  Web pages either time out or load very slowly when the CSS is configured to forward traffic to the CE.  When the CSS bypasses the CE, or when the client is IE6.0, everything works as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas on what would be different in IE5.5?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Zach&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jan 2004 17:15:36 GMT</pubDate>
    <dc:creator>seilsz</dc:creator>
    <dc:date>2004-01-19T17:15:36Z</dc:date>
    <item>
      <title>Reverse Proxy Cache Problem</title>
      <link>https://community.cisco.com/t5/application-networking/reverse-proxy-cache-problem/m-p/294856#M4557</link>
      <description>&lt;P&gt;I am having problems with IE5.5 clients when reverse proxy caching is configured with a CSS.  The clients are using HTTPS, which is terminated on the CSS.  The CSS then communicates with the CE and the origin server using HTTP.  Web pages either time out or load very slowly when the CSS is configured to forward traffic to the CE.  When the CSS bypasses the CE, or when the client is IE6.0, everything works as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas on what would be different in IE5.5?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Zach&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2004 17:15:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/reverse-proxy-cache-problem/m-p/294856#M4557</guid>
      <dc:creator>seilsz</dc:creator>
      <dc:date>2004-01-19T17:15:36Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse Proxy Cache Problem</title>
      <link>https://community.cisco.com/t5/application-networking/reverse-proxy-cache-problem/m-p/294857#M4558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IE 5.5 doesn't work well with RSTs, so the 'persitence reset remap ' was used . The CSS instead of sending a RST to the client, will simply remap the Server side portion of the flow to the new server.  No reset is sent, the request gets to the proper server. IE 6.0 browsers accept RST's and  the persistence reset remap feature works with it too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Jan 2004 16:18:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/reverse-proxy-cache-problem/m-p/294857#M4558</guid>
      <dc:creator>owillins</dc:creator>
      <dc:date>2004-01-23T16:18:48Z</dc:date>
    </item>
  </channel>
</rss>

