<?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: CSS HTTP to HTTPS redirect in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850929#M16596</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is one way&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;************************** &lt;/P&gt;&lt;P&gt;SERVICE &lt;/P&gt;&lt;P&gt;************************** &lt;/P&gt;&lt;P&gt;service secure-transfer &lt;/P&gt;&lt;P&gt;  ip address 2.2.2.2 &lt;/P&gt;&lt;P&gt;  keepalive type none &lt;/P&gt;&lt;P&gt;  type redirect &lt;/P&gt;&lt;P&gt;  no prepend-http &lt;/P&gt;&lt;P&gt;  domain  &lt;A class="jive-link-custom" href="https://my.website.com" target="_blank"&gt;https://my.website.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;  active &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;service regular-server1 &lt;/P&gt;&lt;P&gt;  ip address 10.2.3.4  &lt;/P&gt;&lt;P&gt;  active  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;service regular-server2  &lt;/P&gt;&lt;P&gt;  ip address 10.2.3.5  &lt;/P&gt;&lt;P&gt;  active  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;!*************************** &lt;/P&gt;&lt;P&gt;OWNER &lt;/P&gt;&lt;P&gt;*************************** &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;owner CSS-Team &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  content default-redirect &lt;/P&gt;&lt;P&gt;    vip address 206.25.90.84 &lt;/P&gt;&lt;P&gt;    protocol tcp &lt;/P&gt;&lt;P&gt;    port 80 &lt;/P&gt;&lt;P&gt;    url "/*" &lt;/P&gt;&lt;P&gt;    add service secure-transfer &lt;/P&gt;&lt;P&gt;    active &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  content ssl-rule &lt;/P&gt;&lt;P&gt;    vip address 206.25.90.84 &lt;/P&gt;&lt;P&gt;    protocol tcp &lt;/P&gt;&lt;P&gt;    port 443 &lt;/P&gt;&lt;P&gt;    add service regular-server1 &lt;/P&gt;&lt;P&gt;    add service regular-server2 &lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Jan 2008 09:08:20 GMT</pubDate>
    <dc:creator>diro</dc:creator>
    <dc:date>2008-01-31T09:08:20Z</dc:date>
    <item>
      <title>CSS HTTP to HTTPS redirect</title>
      <link>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850928#M16595</link>
      <description>&lt;P&gt;How do you configure a redirect on the CSS content rules? I want traffic that is destined for &lt;A class="jive-link-custom" href="http://my.website.com" target="_blank"&gt;http://my.website.com&lt;/A&gt; to be redirected to &lt;A class="jive-link-custom" href="https://my.website.com." target="_blank"&gt;https://my.website.com.&lt;/A&gt; I have found references to using a redirect service but it will not let me redirect to an address that is being used as a local VIP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jan 2008 18:57:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850928#M16595</guid>
      <dc:creator>tjcouey</dc:creator>
      <dc:date>2008-01-30T18:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: CSS HTTP to HTTPS redirect</title>
      <link>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850929#M16596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is one way&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;************************** &lt;/P&gt;&lt;P&gt;SERVICE &lt;/P&gt;&lt;P&gt;************************** &lt;/P&gt;&lt;P&gt;service secure-transfer &lt;/P&gt;&lt;P&gt;  ip address 2.2.2.2 &lt;/P&gt;&lt;P&gt;  keepalive type none &lt;/P&gt;&lt;P&gt;  type redirect &lt;/P&gt;&lt;P&gt;  no prepend-http &lt;/P&gt;&lt;P&gt;  domain  &lt;A class="jive-link-custom" href="https://my.website.com" target="_blank"&gt;https://my.website.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;  active &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;service regular-server1 &lt;/P&gt;&lt;P&gt;  ip address 10.2.3.4  &lt;/P&gt;&lt;P&gt;  active  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;service regular-server2  &lt;/P&gt;&lt;P&gt;  ip address 10.2.3.5  &lt;/P&gt;&lt;P&gt;  active  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;!*************************** &lt;/P&gt;&lt;P&gt;OWNER &lt;/P&gt;&lt;P&gt;*************************** &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;owner CSS-Team &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  content default-redirect &lt;/P&gt;&lt;P&gt;    vip address 206.25.90.84 &lt;/P&gt;&lt;P&gt;    protocol tcp &lt;/P&gt;&lt;P&gt;    port 80 &lt;/P&gt;&lt;P&gt;    url "/*" &lt;/P&gt;&lt;P&gt;    add service secure-transfer &lt;/P&gt;&lt;P&gt;    active &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  content ssl-rule &lt;/P&gt;&lt;P&gt;    vip address 206.25.90.84 &lt;/P&gt;&lt;P&gt;    protocol tcp &lt;/P&gt;&lt;P&gt;    port 443 &lt;/P&gt;&lt;P&gt;    add service regular-server1 &lt;/P&gt;&lt;P&gt;    add service regular-server2 &lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 09:08:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850929#M16596</guid>
      <dc:creator>diro</dc:creator>
      <dc:date>2008-01-31T09:08:20Z</dc:date>
    </item>
    <item>
      <title>Re: CSS HTTP to HTTPS redirect</title>
      <link>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850930#M16597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a00801de8d6.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_example09186a00801de8d6.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 09:28:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850930#M16597</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2008-01-31T09:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: CSS HTTP to HTTPS redirect</title>
      <link>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850931#M16598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;But i'm using an ssl-proxy-list. I thought that i had to use the port 80 content rule to direct the proxy list traffic to a port 80 backend server. How would it be done in that case?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 15:12:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850931#M16598</guid>
      <dc:creator>tjcouey</dc:creator>
      <dc:date>2008-01-31T15:12:40Z</dc:date>
    </item>
    <item>
      <title>Re: CSS HTTP to HTTPS redirect</title>
      <link>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850932#M16599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you need to redirect the decrypted traffic to a different port (ie: 81).&lt;/P&gt;&lt;P&gt;So you keep the 80 rule to redirect to https.&lt;/P&gt;&lt;P&gt;The https rule decrypt and forward to the 81 rule which loadbalances to the server on port 80 (don't forget to setup the service with 'port 80').&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, 31 Jan 2008 16:29:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css-http-to-https-redirect/m-p/850932#M16599</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2008-01-31T16:29:32Z</dc:date>
    </item>
  </channel>
</rss>

