<?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 ACE Module URI Rewriting in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407799#M29296</link>
    <description>&lt;P&gt;We are using a Ace module running version 3.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We do have a service which can now be reached by a url like &lt;A href="https://www.xxx.com/yyy/"&gt;https://www.xxx.com/yyy/&lt;/A&gt; &amp;lt; notice the last /&lt;/P&gt;&lt;P&gt;This is running via the Ace which terminates SSL and so on..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now our client wants an url like&amp;nbsp; &lt;A href="https://www.yyy.com"&gt;https://www.yyy.com&lt;/A&gt; . The backend realservers and place of virtual dirs on IIS stays the same. /yyy/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now /yyy/ needs to be added to the backend realserver request, so the correct virtual dir is used. Therfore I need to add this Uri towards the realserver.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea's. ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx Eddie&lt;/P&gt;</description>
    <pubDate>Wed, 17 Feb 2010 16:00:53 GMT</pubDate>
    <dc:creator>eddiemeijer</dc:creator>
    <dc:date>2010-02-17T16:00:53Z</dc:date>
    <item>
      <title>ACE Module URI Rewriting</title>
      <link>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407799#M29296</link>
      <description>&lt;P&gt;We are using a Ace module running version 3.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We do have a service which can now be reached by a url like &lt;A href="https://www.xxx.com/yyy/"&gt;https://www.xxx.com/yyy/&lt;/A&gt; &amp;lt; notice the last /&lt;/P&gt;&lt;P&gt;This is running via the Ace which terminates SSL and so on..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now our client wants an url like&amp;nbsp; &lt;A href="https://www.yyy.com"&gt;https://www.yyy.com&lt;/A&gt; . The backend realservers and place of virtual dirs on IIS stays the same. /yyy/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now /yyy/ needs to be added to the backend realserver request, so the correct virtual dir is used. Therfore I need to add this Uri towards the realserver.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea's. ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx Eddie&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2010 16:00:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407799#M29296</guid>
      <dc:creator>eddiemeijer</dc:creator>
      <dc:date>2010-02-17T16:00:53Z</dc:date>
    </item>
    <item>
      <title>Re: ACE Module URI Rewriting</title>
      <link>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407800#M29297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eddie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently, the ACE will not allow you to re-write a URL on the fly, however, it will allow you to add/remove/re-write HTTP headers and perform redirects to the paths you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if you make this change, you'll also want to account for folks that have the old URL bookmarked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If they come into the ACE requesting &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://www.xxx.com/yyy"&gt;https://www.xxx.com/yyy&lt;/A&gt;&lt;SPAN&gt; then you would use a redirect such as:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;rserver redirect REDIRECT-XXX-TO-YYY&lt;BR /&gt;&lt;SPAN&gt; webhost-redirection &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.cisco.com/"&gt;https://www.yyy.com%p&lt;/A&gt;&lt;SPAN&gt; 301&lt;/SPAN&gt;&lt;BR /&gt; inservice&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the above example, the /yyy would be preserved in the request so that it would still be there when it got load balanced to the rserver that requires it.&amp;nbsp; Only the hostname would be changed from xxx to yyy. A redirect rserver is documented &lt;A href="http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/rsfarms.html#wp1013201"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;On the other hand, to meet your current requirement, if someone comes to the ACE requesting &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://www.yyy.com/"&gt;https://www.yyy.com/&lt;/A&gt;&lt;SPAN&gt; then you could redirect them as follows:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;rserver redirect REDIRECT--YYY&lt;BR /&gt;&lt;SPAN&gt; webhost-redirection &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.cisco.com/"&gt;https://%h/yyy&lt;/A&gt;&lt;SPAN&gt; 301&lt;/SPAN&gt;&lt;BR /&gt; inservice&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Although they would only connect to the hostname, they would be transparently redirected to the URL your IIS server needs. This would be used if the IIS server wants to see &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://www.yyy.com/yyy"&gt;https://www.yyy.com/yyy&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Now, if your IIS server still needs the hostname to be &lt;A href="https://community.cisco.com/www.xxx.com" target="_blank"&gt;www.xxx.com&lt;/A&gt; but with the /yyy at the end, then you could re-write the HOST header from &lt;A href="https://community.cisco.com/www.yyy.com" target="_blank"&gt;www.yyy.com&lt;/A&gt; to &lt;A href="https://community.cisco.com/www.xxx.com" target="_blank"&gt;www.xxx.com&lt;/A&gt;. This would be if your IIS server wants to see &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://www.yyy.com/yyy"&gt;https://www.yyy.com/yyy&lt;/A&gt;&lt;SPAN&gt;.&amp;nbsp; Header Re-Write is documented &lt;/SPAN&gt;&lt;A href="http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/classlb.html#wp1151822"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Feb 2010 17:41:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407800#M29297</guid>
      <dc:creator>Sean Merrow</dc:creator>
      <dc:date>2010-02-17T17:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: ACE Module URI Rewriting</title>
      <link>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407801#M29298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sean,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: &amp;quot;Arial&amp;quot;, &amp;quot;sans-serif&amp;quot;; color: #333333; font-size: 10pt;"&gt;Can you elaborate on the configuration a little more please, i am attempting to do the same thing but my rewrite config matches the traffic again when it returns and so loops, you can see the hits on the redirect server are 2000ish for one web request. My class map is matching on ip and port. I can’t seem to implement a policy map that doesn’t match and ip/port.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Mar 2011 11:48:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407801#M29298</guid>
      <dc:creator>chris</dc:creator>
      <dc:date>2011-03-03T11:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: ACE Module URI Rewriting</title>
      <link>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407802#M29299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sean,&lt;/P&gt;&lt;P&gt;I read your answer that the ACE currently cannot rewrite an url on the fly.&lt;/P&gt;&lt;P&gt;Has anything changed since you wrote that answer? Is it implemented in new versions? Or will it be?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 May 2011 08:12:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407802#M29299</guid>
      <dc:creator>tvirtanen</dc:creator>
      <dc:date>2011-05-19T08:12:34Z</dc:date>
    </item>
    <item>
      <title>Re: ACE Module URI Rewriting</title>
      <link>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407803#M29300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Th&lt;SPAN style="background-color: #f8fafd;"&gt;is has not changed. The ACE including the ACE30 module does not support rewrite of the URL only the headers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Jim&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 May 2011 13:14:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-module-uri-rewriting/m-p/1407803#M29300</guid>
      <dc:creator>jsirstin</dc:creator>
      <dc:date>2011-05-19T13:14:14Z</dc:date>
    </item>
  </channel>
</rss>

