<?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 CSS SSL re-write in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-ssl-re-write/m-p/323553#M5281</link>
    <description>&lt;P&gt;I am in the process of replacing my present css with the newer 11503s with SSl offload capability.  I did some initial testing and was unable to perform the url rewrite.  I did some research and found that the web server must give a 300 code redirect to make the CSS re-write and HTTP link.  &lt;/P&gt;&lt;P&gt;  Is therea design plan available which will allow the web server, which doesn't send a 300 code for an link- especially the ones with HREF- the ability to convert http to https and still maintain the session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to use 2 CSS11503s in a one arm design, with the css performing the SSL offload.  The css encrypts the first page, but doesn't encrypt the links which use HREF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 23 Jan 2005 03:43:32 GMT</pubDate>
    <dc:creator>wilsons5</dc:creator>
    <dc:date>2005-01-23T03:43:32Z</dc:date>
    <item>
      <title>CSS SSL re-write</title>
      <link>https://community.cisco.com/t5/application-networking/css-ssl-re-write/m-p/323553#M5281</link>
      <description>&lt;P&gt;I am in the process of replacing my present css with the newer 11503s with SSl offload capability.  I did some initial testing and was unable to perform the url rewrite.  I did some research and found that the web server must give a 300 code redirect to make the CSS re-write and HTTP link.  &lt;/P&gt;&lt;P&gt;  Is therea design plan available which will allow the web server, which doesn't send a 300 code for an link- especially the ones with HREF- the ability to convert http to https and still maintain the session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to use 2 CSS11503s in a one arm design, with the css performing the SSL offload.  The css encrypts the first page, but doesn't encrypt the links which use HREF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 23 Jan 2005 03:43:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-ssl-re-write/m-p/323553#M5281</guid>
      <dc:creator>wilsons5</dc:creator>
      <dc:date>2005-01-23T03:43:32Z</dc:date>
    </item>
    <item>
      <title>Re: CSS SSL re-write</title>
      <link>https://community.cisco.com/t5/application-networking/css-ssl-re-write/m-p/323554#M5282</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The SCA is the only ssl offloader that will rewrite any HREF.&lt;/P&gt;&lt;P&gt;But this requires inspection of every packet sent by the server and has a huge impact on performance.&lt;/P&gt;&lt;P&gt;Therefore nobody uses this feature except people for which performance is not a requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, in your case, you should redesign your webserver to send correct HREF.&lt;/P&gt;&lt;P&gt;You should never use direct link like &lt;A class="jive-link-custom" href="http://" target="_blank"&gt;http://&lt;/A&gt;.... but instead relative link like ../../...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Jan 2005 14:43:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-ssl-re-write/m-p/323554#M5282</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-01-23T14:43:57Z</dc:date>
    </item>
  </channel>
</rss>

