<?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 HTTPS port re-direction Question in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797937#M15486</link>
    <description>&lt;P&gt;We're currently running a pair of web servers behind a CSS, on the web servers we're running multiple environments which we're differentiating between through port No's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing we'd like to be able to accomplish is to decrypt incoming traffic on port 443 and redirect this to another port No, eg 9443. Is this something I'm able to achieve on the CSS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm thinking I'd have a content rule to terminate the 443 connection which would include a redirect statement, then a rule to allow the connection in on 9443. In the scenario, security isn't really the main issue (it will be internal connectivity) it's more to allow us to test the functionality and allow us to segregate the traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA Dan&lt;/P&gt;</description>
    <pubDate>Wed, 01 Aug 2007 09:04:44 GMT</pubDate>
    <dc:creator>Daniel Anderson</dc:creator>
    <dc:date>2007-08-01T09:04:44Z</dc:date>
    <item>
      <title>HTTPS port re-direction Question</title>
      <link>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797937#M15486</link>
      <description>&lt;P&gt;We're currently running a pair of web servers behind a CSS, on the web servers we're running multiple environments which we're differentiating between through port No's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing we'd like to be able to accomplish is to decrypt incoming traffic on port 443 and redirect this to another port No, eg 9443. Is this something I'm able to achieve on the CSS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm thinking I'd have a content rule to terminate the 443 connection which would include a redirect statement, then a rule to allow the connection in on 9443. In the scenario, security isn't really the main issue (it will be internal connectivity) it's more to allow us to test the functionality and allow us to segregate the traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA Dan&lt;/P&gt;</description>
      <pubDate>Wed, 01 Aug 2007 09:04:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797937#M15486</guid>
      <dc:creator>Daniel Anderson</dc:creator>
      <dc:date>2007-08-01T09:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS port re-direction Question</title>
      <link>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797938#M15487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can have the css listen on port 443 and the server listening on port 9443.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simply specify which port to use under the service definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no need for the CSS to decrypt the traffic or send a redirect for this to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service HTTPS1&lt;/P&gt;&lt;P&gt;  ip x.x.x.x&lt;/P&gt;&lt;P&gt;  port 9443&lt;/P&gt;&lt;P&gt;  active&lt;/P&gt;&lt;P&gt;owner mycompany&lt;/P&gt;&lt;P&gt;  content ssl&lt;/P&gt;&lt;P&gt;    vip x.x.x.x&lt;/P&gt;&lt;P&gt;    add service HTTPS1&lt;/P&gt;&lt;P&gt;    port 9443&lt;/P&gt;&lt;P&gt;    proto tcp&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Aug 2007 11:40:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797938#M15487</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2007-08-01T11:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS port re-direction Question</title>
      <link>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797939#M15488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would this also be the same for http re-direction. For example, I'd like to initiate a connection to a URL, but the servers behind the content rule would only accept connections on port 9080 (different environments). Would the following config function:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service HTTP1 &lt;/P&gt;&lt;P&gt;ip x.x.x.x &lt;/P&gt;&lt;P&gt;port 80 &lt;/P&gt;&lt;P&gt;active &lt;/P&gt;&lt;P&gt;owner mycompany &lt;/P&gt;&lt;P&gt;vip x.x.x.x &lt;/P&gt;&lt;P&gt;add service HTTP1 &lt;/P&gt;&lt;P&gt;port 9080&lt;/P&gt;&lt;P&gt;proto tcp &lt;/P&gt;&lt;P&gt;active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Aug 2007 08:38:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797939#M15488</guid>
      <dc:creator>Daniel Anderson</dc:creator>
      <dc:date>2007-08-09T08:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS port re-direction Question</title>
      <link>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797940#M15489</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if the server behing is listening on port 9080, that's the port you need to configure on the service.&lt;/P&gt;&lt;P&gt;The client will have to use the port in the content rule.&lt;/P&gt;&lt;P&gt;The css will translate from the port in the content to the port in the service.&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, 09 Aug 2007 19:17:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/https-port-re-direction-question/m-p/797940#M15489</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2007-08-09T19:17:58Z</dc:date>
    </item>
  </channel>
</rss>

