<?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: Load balance using HTTP MSISDN number with non RFC HTTP HEAD in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/176727#M2265</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A Cisco CSS 11000 series content services switch periodically sends a keepalive message to a service to determine whether the state of the service is alive, dying, or dead. You can use a keepalive as a health check to make sure the service is up so that the CSS 11000 can use the service for load balancing. Otherwise the CSS 11000 removes the service from the load-balancing algorithm. An advanced (Layer 5) type of keepalive is a Hypertext Transfer Protocol (HTTP) that uses an HTTP HEAD (default) or HTTP GET method. A CSS 11000 running software Cisco Web Network Services (WebNS) Software Release 4.10 or later that uses HTTP keepalive expects the response packet in a specific format.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Dec 2002 16:49:15 GMT</pubDate>
    <dc:creator>ssoberlik</dc:creator>
    <dc:date>2002-12-19T16:49:15Z</dc:date>
    <item>
      <title>Load balance using HTTP MSISDN number with non RFC HTTP HEADER</title>
      <link>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/176726#M2264</link>
      <description>&lt;P&gt;Funtion in the css11000 support load balance over number A in the HTTP header, but dones't work if a proxy gateway send non standar RFC.&lt;/P&gt;&lt;P&gt;Example standar says :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MSISDN: Mobile phone number&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Proxy openwave send this header : x-up-calling-line-id: Mobile phone number&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSS don't balance in this conditions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any solution?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Fri, 13 Dec 2002 11:57:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/176726#M2264</guid>
      <dc:creator>mcusine</dc:creator>
      <dc:date>2002-12-13T11:57:11Z</dc:date>
    </item>
    <item>
      <title>Re: Load balance using HTTP MSISDN number with non RFC HTTP HEAD</title>
      <link>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/176727#M2265</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A Cisco CSS 11000 series content services switch periodically sends a keepalive message to a service to determine whether the state of the service is alive, dying, or dead. You can use a keepalive as a health check to make sure the service is up so that the CSS 11000 can use the service for load balancing. Otherwise the CSS 11000 removes the service from the load-balancing algorithm. An advanced (Layer 5) type of keepalive is a Hypertext Transfer Protocol (HTTP) that uses an HTTP HEAD (default) or HTTP GET method. A CSS 11000 running software Cisco Web Network Services (WebNS) Software Release 4.10 or later that uses HTTP keepalive expects the response packet in a specific format.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Dec 2002 16:49:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/176727#M2265</guid>
      <dc:creator>ssoberlik</dc:creator>
      <dc:date>2002-12-19T16:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: Load balance using HTTP MSISDN number with non RFC HTTP HEAD</title>
      <link>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/176728#M2266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your answer, but not apply to my problem. The problem not is the keepalive packets, the problem is the MSISDN function that no support http headers with non standar format.&lt;/P&gt;&lt;P&gt;Mauricio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Dec 2002 07:47:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/176728#M2266</guid>
      <dc:creator>mcusine</dc:creator>
      <dc:date>2002-12-20T07:47:03Z</dc:date>
    </item>
    <item>
      <title>Re: Load balance using HTTP MSISDN number with non RFC HTTP HEADER</title>
      <link>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/3909748#M51140</link>
      <description />
      <pubDate>Sun, 18 Aug 2019 02:28:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/load-balance-using-http-msisdn-number-with-non-rfc-http-header/m-p/3909748#M51140</guid>
      <dc:creator>+9660505150940</dc:creator>
      <dc:date>2019-08-18T02:28:05Z</dc:date>
    </item>
  </channel>
</rss>

