Extended list of status-/errorcodes from webapps

[Eli Stair]

Making changes to the HTTP header to indicate an errorcode is something 
I haven't thought about before.  I've always used tags in the HTML body 
to indicate the issue... it requires less work, and enables you to be 
more verbose (and IMO is cleaner than extending the standard for the 
header...).

What need is making you lean more towards this modification rather than 
just having your status applet/URL output the relavent data in the body 
for parsing?

/eli


Morten Werner Olsen wrote:
> Hi!
> 
> This isn't directly related to Nagios, but I assume some of you use
> Nagios for monitoring webapplications so still kind of related. :)
> 
> We've recently started to monitor our webservers and some of our
> webapplications with Nagios. Most webapplications depends on other
> services as databases, LDAP, NIS, filesystems and so on. Together with
> the webappdevelopers we are planning to make a status-page in the most
> important webapps which tests these dependencies, and print the status
> either in the output or in one of the HTML-headers.
> 
> My first thought was to extend the Status-header (which normally says
> '200 OK'). I googled around to see if I could find an already written
> extention to this standard [1], but didn't find any. There are also
> other problems with this solution; PHP denies to print "invalid
> headers" not defined by the standard, and the check_http-plugin for
> Nagios reports "Critical - invalid header".
> 
> So after speaking to a few of my colleagues, we agreed that using an
> own header ("App-status:" or something) might be the best
> solution. But I would like to know if any others have done anything
> like this? And have anyone made such a list of status-codes available
> or even proposed it as a standard?
> 
> I'm also interested if some of you have other smart solutions to this
> "problem"?
> 
> 
> - Werner
> 
> [1] http://www.ietf.org/rfc/rfc2616.txt
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null