<?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: css11500 in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/css11500/m-p/176936#M2268</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cheng,&lt;/P&gt;&lt;P&gt;If you are using a http keepalive then yes we can mark the server up or down depending on the response.  If we get a response code back for a specific defined url other than 200OK then we will mark the server down.&lt;/P&gt;&lt;P&gt;If you are asking can me monitor every requestion for a 404 then the answer is no.&lt;/P&gt;&lt;P&gt;You can send a client to a customised error page if all services are down on a particular content rule.  This is done by using the command&lt;/P&gt;&lt;P&gt;primary sorry server&lt;/P&gt;&lt;P&gt;Under the content rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 14 Dec 2002 05:53:43 GMT</pubDate>
    <dc:creator>lynchp</dc:creator>
    <dc:date>2002-12-14T05:53:43Z</dc:date>
    <item>
      <title>css11500</title>
      <link>https://community.cisco.com/t5/application-networking/css11500/m-p/176935#M2267</link>
      <description>&lt;P&gt;Can css11500 monitors whether a server is sending 404 errors or customized error pages ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any response.&lt;/P&gt;&lt;P&gt;Cheng&lt;/P&gt;</description>
      <pubDate>Fri, 13 Dec 2002 13:40:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css11500/m-p/176935#M2267</guid>
      <dc:creator>cheng.ung</dc:creator>
      <dc:date>2002-12-13T13:40:56Z</dc:date>
    </item>
    <item>
      <title>Re: css11500</title>
      <link>https://community.cisco.com/t5/application-networking/css11500/m-p/176936#M2268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cheng,&lt;/P&gt;&lt;P&gt;If you are using a http keepalive then yes we can mark the server up or down depending on the response.  If we get a response code back for a specific defined url other than 200OK then we will mark the server down.&lt;/P&gt;&lt;P&gt;If you are asking can me monitor every requestion for a 404 then the answer is no.&lt;/P&gt;&lt;P&gt;You can send a client to a customised error page if all services are down on a particular content rule.  This is done by using the command&lt;/P&gt;&lt;P&gt;primary sorry server&lt;/P&gt;&lt;P&gt;Under the content rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Dec 2002 05:53:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css11500/m-p/176936#M2268</guid>
      <dc:creator>lynchp</dc:creator>
      <dc:date>2002-12-14T05:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: css11500</title>
      <link>https://community.cisco.com/t5/application-networking/css11500/m-p/176937#M2269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are about to depoly a pair of CSS11500s. &lt;/P&gt;&lt;P&gt;I was under the impression we can create a web status page on our web service (created by a monitoring cgi program), and get the CSS to make a hash of the returned contents of the page.&lt;/P&gt;&lt;P&gt;If that page changes in any way (i.e. the cgi creating the page detects a failure in the application at some point) then the CSS will retrieve the page, hash it again, and note the hash value has changed.&lt;/P&gt;&lt;P&gt;In this case it would then redirect all site traffic to the sorry server, which I think is what the original poster wants.&lt;/P&gt;&lt;P&gt;Have I got this wrong?!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2002 14:27:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/css11500/m-p/176937#M2269</guid>
      <dc:creator>squigg</dc:creator>
      <dc:date>2002-12-17T14:27:29Z</dc:date>
    </item>
  </channel>
</rss>

