Hello Dirk,

when is this Beat final ?
Normally, i don't like Beta's.

But i don't mix tcp- and URL ckeck, i only use URL-check.
But the software mixes it ?

Bernd


 

> -----Original Message-----
> From: Servers Alive Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
> Sent: Thursday, October 11, 2007 2:51 PM
> To: Servers Alive Discussion List
> Subject: RE: [SA-list] how to check SSL-Sites
> 
> 
> Wait I think I understand the problem now.
> In some situation with 6.0.2056 the TCP and URL check get 
> mixed up and that is what you're getting now. In the current 
> beta build this is fixed http://Beta.woodstone.nu
> 
> 
> Dirk Bulinckx. 
> 
> -----Original Message-----
> From: Servers Alive Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Lentes, Bernd
> Sent: Thursday, October 11, 2007 2:41 PM
> To: Servers Alive Discussion List
> Subject: RE: [SA-list] how to check SSL-Sites
> 
> Hello Dirk,
> 
> The content is a lot of javascript which is not visible in 
> the browser. The excerp was from the logfile. I'm just 
> checking the URL https://fqdn:50000 with "GET", "should 
> contain" "exact this phrase" and then an empty field. Is this wrong ?
> 
> Bernd
> 
> 
> -- 
> Bernd Lentes
> staatl. geprüfter Techniker
> Systemadministration
> Institut für Entwicklungsgenetik
> GSF
> Raum 35/1008f
> Ingolstädter Landstraße 1
> 85764 München-Neuherberg
> mailto:[EMAIL PROTECTED]
> phoneto:089/3187-1241
> faxto:089/3187-3826
> http://www.gsf.de/idg
> 
> 
>  
> 
> > -----Original Message-----
> > From: Servers Alive Discussion List
> > [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
> > Sent: Thursday, October 11, 2007 2:21 PM
> > To: Servers Alive Discussion List
> > Subject: RE: [SA-list] how to check SSL-Sites
> > 
> > 
> > SA is able to check SSL sites, on a none-standard port and
> > with a self-signed cert. From what I see in the log you're 
> > also checking the actual content. Correct? Does the content 
> > that you're looking for is visible within the received page 
> > (as per logfile)?
> > 
> > Dirk Bulinckx.
> > 
> > -----Original Message-----
> > From: Servers Alive Discussion List
> > [mailto:[EMAIL PROTECTED] On Behalf Of Lentes, Bernd
> > Sent: Thursday, October 11, 2007 2:10 PM
> > To: Servers Alive Discussion List
> > Subject: [SA-list] how to check SSL-Sites
> > 
> > hello ML,
> > 
> > i'm using SA 6.0.2056 on XP Prof. SP2.
> > I'm checking 12 entries. One is a HP System Insight Manager
> > Webserver (which monitors itself ProLiant Servers). This is 
> > running as a webserver, using secure connection (https), and 
> > it listens on port 50000. The certficate is self-signed. Firt 
> > i just checked the url https://fqdn:50000 , which seemed to 
> > work in the beginning. But sometimes the response was not 
> > o.k., as the log said:
> > Excerp:
> > -----------
> > Connection possible, but received data not correct (
> > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 
> > Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";>
> > <html class="signInPage">
> >     <head>
> >         <title>HP Systems Insight Manager</title>
> > 
> >         <link type='text/css' rel='stylesheet'
> > href='/mxhtml/css/default.css'> ....
> > 
> > -----------
> > It follows the whole sourcecode from this webpage, which is a 
> > lot, because a lot of JS is included in this page. Because 
> > this happens several times a day, i got logs of 5-10MB per 
> > day ! And today SA stopped running, i believe because of 
> > that. The service was just stopping.
> > 
> > How can i check SSL-encrypted pages with a self-signed
> > certificate reliable ? And without getting big log-files ?
> > 
> > Thank you.
> > 
> > Bernd
> > 
> > --
> > Bernd Lentes
> > staatl. geprüfter Techniker
> > Systemadministration
> > Institut für Entwicklungsgenetik
> > GSF
> > Raum 35/1008f
> > Ingolstädter Landstraße 1
> > 85764 München-Neuherberg
> > mailto:[EMAIL PROTECTED]
> > phoneto:089/3187-1241
> > faxto:089/3187-3826
> > http://www.gsf.de/idg
> > 
> > 
> >  
> > 
> > To unsubscribe send a message with UNSUBSCRIBE as subject to
> > [email protected] If you use auto-responders (like 
> > out-of-the-office messages), then make sure that they are not 
> > send to the list nor to the individual members of the list 
> > that send a message.  Doing this will get you removed from the list.
> > 
> > To unsubscribe send a message with UNSUBSCRIBE as subject to
> > [email protected] If you use auto-responders (like 
> > out-of-the-office messages), then make sure that they are not 
> > send to the list nor to the individual members of the list 
> > that send a message.  Doing this will get you removed from the list.
> > 
> 
> To unsubscribe send a message with UNSUBSCRIBE as subject to 
> [email protected]
> If you use auto-responders (like out-of-the-office messages), 
> then make sure
> that they are not send to the list nor to the individual 
> members of the list
> that send a message.  Doing this will get you removed from the list.
> 
> To unsubscribe send a message with UNSUBSCRIBE as subject to 
> [email protected]
> If you use auto-responders (like out-of-the-office messages), 
> then make sure that they are not send to the list nor to the 
> individual members of the list that send a message.  Doing 
> this will get you removed from the list.
> 

To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure 
that they are not send to the list nor to the individual members of the list 
that send a message.  Doing this will get you removed from the list.

Reply via email to