<?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 HTTP Header Port Rewrite in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162212#M39735</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Eric,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe you want to see the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/thread/2035408"&gt;https://supportforums.cisco.com/thread/2035408&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jorge&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 Apr 2013 22:45:53 GMT</pubDate>
    <dc:creator>Jorge Bejarano</dc:creator>
    <dc:date>2013-04-09T22:45:53Z</dc:date>
    <item>
      <title>ACE HTTP Header Port Rewrite</title>
      <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162209#M39732</link>
      <description>&lt;P&gt;What is the syntax for rewriting the destination port for a HTTP request?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For Example: Rewriting "&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.test.com" rel="nofollow"&gt;http://www.test123.com&lt;/A&gt;&lt;SPAN&gt;" TO "&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.test.com:81" rel="nofollow"&gt;http://www.test123.com:81&lt;/A&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2013 13:28:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162209#M39732</guid>
      <dc:creator>ericojijo</dc:creator>
      <dc:date>2013-04-09T13:28:45Z</dc:date>
    </item>
    <item>
      <title>ACE HTTP Header Port Rewrite</title>
      <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162210#M39733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The simple solution is to specify port at rserver level to the desired port. In your case it should be like this : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;host1/Admin(config-sfarm-host)# &lt;STRONG&gt;rserver SERVER1 81&lt;/STRONG&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is from the documentation which explain the same: &lt;/P&gt;&lt;H3&gt; Associating a Real Server with a Server Farm &lt;/H3&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1000365"&gt;&lt;/A&gt;&lt;A name="wpmkr1000364"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt; You can associate one or more real servers with a server farm and enter real-server server-farm configuration mode by using the &lt;STRONG&gt;rserver&lt;/STRONG&gt; command in either server farm host or server farm redirect&amp;nbsp; configuration mode. The real server must already exist. For information&amp;nbsp; about configuring a real server, see the &lt;A href="http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA1_7_/configuration/slb/guide/rsfarms.html#wp999506"&gt;"Configuring Real Servers"&lt;/A&gt; section. You can configure a maximum of 16,384 real servers in a server farm. The syntax of this command is as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1000369"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt;rserver &lt;EM style="font-style: italic; font-weight: normal;"&gt;name&lt;/EM&gt; [&lt;EM style="font-style: italic; font-weight: normal;"&gt;port&lt;/EM&gt;] &lt;/P&gt;&lt;P&gt;&lt;A name="wp1000370"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt; The arguments are as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1000371"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;&lt;EM&gt;name&lt;/EM&gt;—Unique&amp;nbsp; identifier of an existing real server. Enter an unquoted text string&amp;nbsp; with no spaces and a maximum of 64 alphanumeric characters. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1000372"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt; •&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;&lt;EM&gt;port&lt;/EM&gt;—(Optional) Port number used for the real server port address translation (PAT). Enter an integer from 1 to 65535. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1013304"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;If you choose not to assign a port number for the real server&amp;nbsp; association with the server farm, the default behavior by the ACE is to&amp;nbsp; automatically assign the same destination port that was used by the&amp;nbsp; inbound connection to the outbound server connection.&lt;/STRONG&gt; For example, if&amp;nbsp; the incoming connection to the ACE is a secure client HTTPS connection,&amp;nbsp; the connection is typically made on port 443. If you do not assign a&amp;nbsp; port number to the real server, the ACE will automatically use port 443&amp;nbsp; to connect to the server, which results in the ACE making a clear-text&amp;nbsp; HTTP connection over port 443. In this case, you would typically define&amp;nbsp; an outbound destination port of 80, 81, or 8080 for the backend server&amp;nbsp; connection. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1000373"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt; For example, to identify real server SERVER1 and specify port 80 for the outgoing connection, enter: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A name="wp1000374"&gt;&lt;/A&gt; &lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;host1/Admin(config-sfarm-host)# &lt;STRONG&gt;rserver SERVER1 80
&lt;/STRONG&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;&lt;A name="wp1000375"&gt;&lt;/A&gt; &lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;host1/Admin(config-sfarm-host-rs)#
&lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards, &lt;/P&gt;&lt;P&gt;Ajay Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2013 14:45:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162210#M39733</guid>
      <dc:creator>ajayku2</dc:creator>
      <dc:date>2013-04-09T14:45:02Z</dc:date>
    </item>
    <item>
      <title>ACE HTTP Header Port Rewrite</title>
      <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162211#M39734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;Thanks Ajay. The server farm hosts are already defined as you described above. The problem I'm having is that the client is attempting to connect to &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.test123:81"&gt;http://www.test123:81&lt;/A&gt;&lt;SPAN&gt;, but the ACE is stripping the port 81, and sennding it to the server on port 80. Any ideas?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2013 15:23:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162211#M39734</guid>
      <dc:creator>ericojijo</dc:creator>
      <dc:date>2013-04-09T15:23:48Z</dc:date>
    </item>
    <item>
      <title>ACE HTTP Header Port Rewrite</title>
      <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162212#M39735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Eric,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe you want to see the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/thread/2035408"&gt;https://supportforums.cisco.com/thread/2035408&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jorge&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2013 22:45:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162212#M39735</guid>
      <dc:creator>Jorge Bejarano</dc:creator>
      <dc:date>2013-04-09T22:45:53Z</dc:date>
    </item>
    <item>
      <title>ACE HTTP Header Port Rewrite</title>
      <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162213#M39736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check if you have configured any rewrite rule or NAT rule. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If possible attach the config and I will have a look. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards, &lt;/P&gt;&lt;P&gt;Ajay Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Apr 2013 07:07:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162213#M39736</guid>
      <dc:creator>ajayku2</dc:creator>
      <dc:date>2013-04-10T07:07:40Z</dc:date>
    </item>
    <item>
      <title>ACE HTTP Header Port Rewrite</title>
      <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162214#M39737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ajay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's no NAT rules configured, but I'll check the configs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Apr 2013 20:01:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162214#M39737</guid>
      <dc:creator>ericojijo</dc:creator>
      <dc:date>2013-04-10T20:01:10Z</dc:date>
    </item>
    <item>
      <title>ACE HTTP Header Port Rewrite</title>
      <link>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162215#M39738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I finally resolved the use by creating a header rewrite action-list, and then applying it to the appropriate policy map:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;action-list type modify http HEADER_REWRITE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; header rewrite request Host header-value "www.test123.com" replace "www.test123.com:81"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your input,&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2013 19:36:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-http-header-port-rewrite/m-p/2162215#M39738</guid>
      <dc:creator>ericojijo</dc:creator>
      <dc:date>2013-04-18T19:36:03Z</dc:date>
    </item>
  </channel>
</rss>

