Good point ... on the other side, there can be users already who use
this test and thus will need to modify the configuration on upgrade.
The redirect test in monit cvs can also identify the loops, which can be
useful.
So here is my +-0 (the proposed change has positive and negative features)
Martin
Jan-Henrik Haukeland wrote:
The HTTP protocol test supports rudimentary redirect within the same
server but not to external servers, though that should not be difficult
to add. However looking at the redirect code now I think the best would
be to remove it from monit. The reason is that it adds extra unnecessary
complexity without adding much in functionality and it also keeps the
socket open for keep-alive timeout. Users should instead write the
direct URL and we should send the "Connection: close" header as well
which would be easier on the server we test. For monit it does not
matter though since the socket is closed anyway after the http protocol
test returns.
Jan-Henrik
_______________________________________________
monit-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monit-dev
_______________________________________________
monit-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monit-dev
