1 |
<HTML> |
<html> |
2 |
<HEAD> |
<head> |
3 |
<!-- $Id$ --> |
<!-- $id: next.html,v 1.28 2003/09/19 03:44:17 hauk exp $ --> |
4 |
<TITLE>Proposal for monit 4.1</TITLE> |
<title>monit::proposal for monit 4.1</title> |
5 |
<link rel="stylesheet" title="Default" type="text/css" href="monit.css"> |
<link rel="stylesheet" title="default" type="text/css" href="monit.css"> |
6 |
</HEAD> |
</head> |
7 |
|
|
8 |
<BODY |
<body |
9 |
BGCOLOR="#ffffff" |
bgcolor="#ffffff" |
10 |
TEXT="#000000" |
text="#000000" |
11 |
ALINK="#fd9630" |
alink="#fd9630" |
12 |
LINK="#0022ff" |
link="#0022ff" |
13 |
VLINK="#0022ff"> |
vlink="#0022ff"> |
14 |
|
|
15 |
<IMG SRC="monit.gif" BORDER=0><BR> |
<a href="index.html"><IMG SRC="monit.gif" BORDER=0></a><p> |
16 |
<HR NOSHADE SIZE=1> |
<table width=100% cellspacing=0 cellpadding=0> <tr><td |
17 |
|
bgcolor="#333333"><img src="pixel.gif" width="1" height="1" |
18 |
<TABLE BGCOLOR="#FFFFFF" CELLPADDING=0 CELLSPACING=0 BORDER=0 > |
alt=""></td></tr></table><p> |
19 |
<TR> |
|
20 |
<TD VALIGN="TOP"> |
|
21 |
|
<table bgcolor="#ffffff" cellpadding=0 cellspacing=0 border=0 > |
22 |
|
<tr> |
23 |
|
<td valign="top"> |
24 |
<!--#include file="menu.html"--> |
<!--#include file="menu.html"--> |
25 |
</TD> |
</td> |
26 |
<TD VALIGN="TOP"> |
<td valign="top"> |
27 |
|
|
28 |
<TABLE CELLPADDING=10 CELLSPACING=10 > |
<table cellpadding=10 cellspacing=10 > |
29 |
<TR> |
<tr> |
30 |
<TD> |
<td> |
31 |
|
|
32 |
<B class=menu>Plans for the next release</B><P><BR><P> |
<b class=menu>Plans for the next release</b><p><br><p> |
33 |
|
|
34 |
|
|
35 |
<b><u>Introduction:</u></b><p> |
<b><u>Introduction:</u></b><p> |
95 |
<br> |
<br> |
96 |
<p> |
<p> |
97 |
|
|
98 |
<li><b>HTTP request returned data checksum</b><br> |
<li><b>HTTP request returned data checksum</b><br> It makes sense now |
99 |
It makes sense now to implement this test, because when monit was designed for |
to implement this test, because when monit was designed for local |
100 |
local tests only, it was possible to checksum the page or script directly in |
tests only, it was possible to checksum the page or script directly in |
101 |
the filesystem. It is not possible to do the same for remote hosts => it will |
the filesystem. With the new remote host test it should be possible to |
102 |
be usefull to support this option, something like:<br><br> |
to do the same for remote documents. For instance.:<br><br> |
103 |
|
|
104 |
<pre> |
<pre> |
105 |
if failed host my.web.org port 80 protocol http and request "/my/page.html" |
if failed host my.web.org port 80 protocol http |
106 |
with checksum 8f7f419955cefa0b33a2ba316cba3659 then alert |
and request "/my/page.html" |
107 |
|
with checksum 8f7f419955cefa0b33a2ba316cba3659 |
108 |
|
then alert |
109 |
</pre> |
</pre> |
110 |
|
|
111 |
It will involve chunked transfer encoding implementation as discussed in the past.<br> |
This will require implementing chunked transfer encoding, as discussed |
112 |
|
in the past.<br> |
113 |
|
|
114 |
<br> |
<br> |
115 |
|
|
130 |
<br> |
<br> |
131 |
<p> |
<p> |
132 |
|
|
133 |
</TD> |
</td> |
134 |
</TR> |
</tr> |
135 |
</TABLE> |
</table> |
136 |
|
|
137 |
|
|
138 |
</TD> |
</td> |
139 |
</TR> |
</tr> |
140 |
</TABLE> |
</table> |
141 |
</BODY> |
</body> |
142 |
</HTML> |
</html> |