<?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: ACE-What is the difference between these two redirects? in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382979#M28770</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the configuration you have posted there is a need for both class-maps, action-list, and redirection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The way this configuration will work is any client attempting to establish an HTTP connection the ACE will preserve the URL, but redirect them to the HTTPS equivalent. ex: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.domain.com/admin"&gt;http://www.domain.com/admin&lt;/A&gt;&lt;SPAN&gt; -----&amp;gt; &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://www.domain.com/admin"&gt;https://www.domain.com/admin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This configuration would be used for the inbound HTTP connections:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rserver redirect WEB-redir&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; webhost-redirection &lt;/SPAN&gt;&lt;A class="jive-link-external-small"&gt;https://%h/%p&lt;/A&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;serverfarm redirect WEB-redir&lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver WEB-redir&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map match-all WEB-VIP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 172.20.100.104 tcp eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match WEB-redir&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; serverfarm WEB-redir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class WEB-redir&lt;BR /&gt;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp; loadbalance policy WEB-redir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the client's connection is redirected to HTTPS, their connection will use this part of the configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;action-list type modify http urlrewrite&lt;BR /&gt;&amp;nbsp; ssl url rewrite location "*"&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;class-map match-all WEB-VIP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 172.20.100.104 tcp eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match WEB-POLICY&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; sticky-serverfarm WEB_cookie&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; action urlrewrite&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class WEB-VIP&lt;BR /&gt;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp; loadbalance policy WEB-POLICY&lt;BR /&gt;&amp;nbsp; loadbalance vip icmp-reply&lt;BR /&gt;&amp;nbsp; ssl-proxy server WEB-SSL-PROXY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The action-list will come into play the moment the web server delivering content for the client attempts to send the client's connection BACK to an HTTP URL.&amp;nbsp; The ACE will re-write the location URL from HTTP to HTTPS to allow the client's connection to stay on an HTTPS page.&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;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Feb 2010 05:09:39 GMT</pubDate>
    <dc:creator>jason.espino</dc:creator>
    <dc:date>2010-02-26T05:09:39Z</dc:date>
    <item>
      <title>ACE-What is the difference between these two redirects?</title>
      <link>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382978#M28769</link>
      <description>&lt;P&gt;My question-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why the need for both the class-map on WWW and HTTPS on the same vip below?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wouldnt the ACE see the incoming port 80 request and redirect it to 443 back to the&lt;/P&gt;&lt;P&gt;client browser with the action-list modify statement in the config and the action url rewrite in the policy statement&lt;/P&gt;&lt;P&gt;of the WEB-POLICY?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Yet is see a redirect statement going to &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.cisco.com/"&gt;https://%h/%p&lt;/A&gt;&lt;SPAN&gt; under the redir serverfarm&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;does this make sense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;action-list type modify http urlrewrite&lt;BR /&gt;&amp;nbsp; ssl url rewrite location "*"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map match-all WEB-VIP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 172.20.100.104 tcp eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map match-all&amp;nbsp; WEB-redir&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 172.20.100.104 tcp eq www&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match WEB-POLICY&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; sticky-serverfarm WEB_cookie&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; action urlrewrite&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match WEB-redir&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; serverfarm WEB-redir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class WEB-VIP&lt;BR /&gt;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp; loadbalance policy WEB-POLICY&lt;BR /&gt;&amp;nbsp; loadbalance vip icmp-reply&lt;BR /&gt;&amp;nbsp; ssl-proxy server WEB-SSL-PROXY&lt;BR /&gt;class WEB-redir&lt;BR /&gt;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp; loadbalance policy WEB-redir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rserver redirect WEB-redir&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; webhost-redirection &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.cisco.com/"&gt;https://%h/%p&lt;/A&gt;&lt;BR /&gt;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;serverfarm redirect WEB-redir&lt;BR /&gt;&amp;nbsp; rserver WEB-redir&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2010 01:02:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382978#M28769</guid>
      <dc:creator>nygenxny123</dc:creator>
      <dc:date>2010-02-26T01:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: ACE-What is the difference between these two redirects?</title>
      <link>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382979#M28770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the configuration you have posted there is a need for both class-maps, action-list, and redirection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The way this configuration will work is any client attempting to establish an HTTP connection the ACE will preserve the URL, but redirect them to the HTTPS equivalent. ex: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.domain.com/admin"&gt;http://www.domain.com/admin&lt;/A&gt;&lt;SPAN&gt; -----&amp;gt; &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://www.domain.com/admin"&gt;https://www.domain.com/admin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This configuration would be used for the inbound HTTP connections:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rserver redirect WEB-redir&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; webhost-redirection &lt;/SPAN&gt;&lt;A class="jive-link-external-small"&gt;https://%h/%p&lt;/A&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;serverfarm redirect WEB-redir&lt;/P&gt;&lt;P&gt;&amp;nbsp; rserver WEB-redir&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map match-all WEB-VIP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 172.20.100.104 tcp eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match WEB-redir&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; serverfarm WEB-redir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class WEB-redir&lt;BR /&gt;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp; loadbalance policy WEB-redir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the client's connection is redirected to HTTPS, their connection will use this part of the configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;action-list type modify http urlrewrite&lt;BR /&gt;&amp;nbsp; ssl url rewrite location "*"&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;class-map match-all WEB-VIP&lt;BR /&gt;&amp;nbsp; 2 match virtual-address 172.20.100.104 tcp eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map type loadbalance first-match WEB-POLICY&lt;BR /&gt;&amp;nbsp; class class-default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; sticky-serverfarm WEB_cookie&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; action urlrewrite&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class WEB-VIP&lt;BR /&gt;&amp;nbsp; loadbalance vip inservice&lt;BR /&gt;&amp;nbsp; loadbalance policy WEB-POLICY&lt;BR /&gt;&amp;nbsp; loadbalance vip icmp-reply&lt;BR /&gt;&amp;nbsp; ssl-proxy server WEB-SSL-PROXY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The action-list will come into play the moment the web server delivering content for the client attempts to send the client's connection BACK to an HTTP URL.&amp;nbsp; The ACE will re-write the location URL from HTTP to HTTPS to allow the client's connection to stay on an HTTPS page.&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;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Feb 2010 05:09:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382979#M28770</guid>
      <dc:creator>jason.espino</dc:creator>
      <dc:date>2010-02-26T05:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: ACE-What is the difference between these two redirects?</title>
      <link>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382980#M28771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thx for the explanation-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;correct me if im wrong&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so if the outside user is coming in on http-the rserver redirect will come into play when the ACE makes it go https:---per my config-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now the url redirect is into play coming in from the server......if the server for some reason sends url info http-the ACE will rewrite it as https-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now ..is it best practice to have both these configs to make sure that all data is always https?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;why would you have one without the other?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can only imagine you wouldnt have the rserver redirect https%h%p if you were not allowing anything coming in on port 80-&lt;/P&gt;&lt;P&gt;since all inbound traffic would be 443?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;however even if you only had 443 open........u would still use the url rewrite because the backend serve may send something back clear text?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;am i right in my conclusion?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Feb 2010 06:40:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382980#M28771</guid>
      <dc:creator>nygenxny123</dc:creator>
      <dc:date>2010-02-27T06:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: ACE-What is the difference between these two redirects?</title>
      <link>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382981#M28772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your understanding of how the configuration works is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To answer your questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Now ..is it best practice to have both these configs to make sure&amp;nbsp; that all data is always https?"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would say so, as the redirect will ALWAYS send the client to an HTTPS site, and the url rewrite will ensure the connection stays on HTTPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"why would you have one without the other?"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This question I can not answer. I'm not sure if the person who owns the site/domain wanted the clients connection to be HTTPS only for security reasons, application reasons, or just personal preference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"I can only&amp;nbsp; imagine you wouldnt have the rserver redirect https%h%p if you were not&amp;nbsp; allowing anything coming in on port 80-&lt;/P&gt;&lt;P&gt;since all inbound traffic&amp;nbsp; would be 443?"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even if there was no HTTP content being served the rserver redirects pupose would ensure the client's connection is redirected to an HTTPS URL that can be processed by the web servers, rather then have the client's connection simply time out on the browser if there was no redirect or port 80 configuration in place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"however&amp;nbsp; even if you only had 443 open........u would still use the url rewrite&amp;nbsp; because the backend serve may send something back clear text?"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is a possiblity. The url rewrite would simply ensure the clients connection remains on HTTPS.&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;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Mar 2010 05:14:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382981#M28772</guid>
      <dc:creator>jason.espino</dc:creator>
      <dc:date>2010-03-01T05:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: ACE-What is the difference between these two redirects?</title>
      <link>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382982#M28773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for the explanation &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 15:50:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-what-is-the-difference-between-these-two-redirects/m-p/1382982#M28773</guid>
      <dc:creator>nygenxny123</dc:creator>
      <dc:date>2010-03-02T15:50:55Z</dc:date>
    </item>
  </channel>
</rss>

