monit-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

monit ./Makefile.in ./gc.c ./l.l ./monitor.h ./...


From: Jan-Henrik Haukeland
Subject: monit ./Makefile.in ./gc.c ./l.l ./monitor.h ./...
Date: Sun, 23 Jan 2005 20:04:36 -0500

CVSROOT:        /cvsroot/monit
Module name:    monit
Branch:         
Changes by:     Jan-Henrik Haukeland <address@hidden>   05/01/24 01:04:36

Modified files:
        .              : Makefile.in gc.c l.l monitor.h p.y 
        protocols      : http.c 

Log message:
        Intermediate checkin for URL content check. This checkin compiles, and
        parse properly the new syntax. The next step is to implement the
        actual content check.
        
        The folowing design decisions are taken:
        
        1) Adding a new "check URL" service statement is dropped. Instead URL
        testing are added as a connection test statement and can be used
        both from a "check process" and preferably a "check host"
        statement. In my opinion there is not a need for a standalone
        "check URL" statement, unless a chain of URL request are to be
        performed and sessions are to be supported. In that case something
        like this could be used:
        
        check URL login http://www.a.com/login
        
        check URL behind_login_1 http://www.a.com/protected1/
        depends on login
        
        2) The http.c protocol test is changed to attempt basic auth if
        required by the server. The test will also try to follow redirects
        from the server.
        
        3) Here's an example on how to use the new URL test including using a
        regular expression to test the content returned from the server:
        
        check host SOL with address www.sol.no
        if failed url
        http://username:address@hidden/index.html?querystring
        and content != "^regexp$"
        with timeout 15 seconds
        then ..
        
        4) When testing a regular expression the content returned from the
        server must be read into a buffer. The buffer is allocated based on
        the response header content-length or if not set on a fixed
        limit. Either way, monit should not be allowed to allocate to large
        a buffer and a max limit on 1Mb will be defined, this is probably
        to much also?

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/monit/monit/Makefile.in.diff?tr1=1.22&tr2=1.23&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/monit/monit/gc.c.diff?tr1=1.59&tr2=1.60&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/monit/monit/l.l.diff?tr1=1.86&tr2=1.87&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/monit/monit/monitor.h.diff?tr1=1.163&tr2=1.164&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/monit/monit/p.y.diff?tr1=1.195&tr2=1.196&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/monit/monit/protocols/http.c.diff?tr1=1.36&tr2=1.37&r1=text&r2=text





reply via email to

[Prev in Thread] Current Thread [Next in Thread]