RE: [Nagios-devel] Nagios and https
Posted: Wed Jul 10, 2002 10:35 pm
I haven't done any research into the actual c code.. but based on your
symptoms, thats what I would expect to find is absolute URL calls. I'm not
sure it's a bug, just undesireable functionality. Maybe there should be a
configuration option or ./configure option that specifies you are using SSL
vs. non-SSL, or simply use relative pathing.
----- Original Message -----
From: "Pritzl, Peter"
To: "'SyBase'"
Sent: Thursday, July 11, 2002 1:00 AM
Subject: RE: [Nagios-devel] Nagios and https
> Aaaaah, so what you are saying is that the cgi's use absolute and not
> relative paths when doing the refresh? Should that be considered a bug?
>
>
> -----Original Message-----
> From: SyBase [mailto:sybase@slashdev.org]
> Sent: 11 July 2002 06:35
> To: Pritzl, Peter
> Subject: Re: [Nagios-devel] Nagios and https
>
>
> This has to do with direct url calls.. most likely CGI's are using
> http://domainname.com/path/page.html while you are using https. This
> would cause the secure and insecure items symptom.. and "page cannot be
> displayed" is probably because you are not running apache (webserver) on
> port 80, or dont have nagios setup in that instance.
>
> ----- Original Message -----
> From: "Pritzl, Peter"
> To:
> Sent: Wednesday, July 10, 2002 8:45 AM
> Subject: [Nagios-devel] Nagios and https
>
>
> > I have noticed that on my installation when running Nagios over https
> > the automatic refresh doesn't work. You'll get a dialog box stating
> > that the page contains both secure and unsecure items. You don't get
> > this if you manual refresh the entire page. Whatever you answer in
> > this dialog box you afterwards get a "page cannot be displayed". It
> > seems to do this with all screens that automaticly refresh Could this
> > be a bug in the CGI?
> >
> >
> > Regards
> > Peter
> >
> >
> ________________________________________________________________________
> ____
> ____________
> >
> > The information in this Internet email is confidential and intended
> > for
> the sole use of the addressee(s). Access, copying, disclosure or
> re-use, in any way, of the information contained in this email by anyone
> other than the
> addressee(s) is unauthorised Internet communication and may not be
> secure.
> >
> > CCC Network Systems, Inc. accepts no legal responsibility for the
> > content
> of the message. Any opinions or views presented are solely the
> responsibility of the author and do not necessarily represent those of
> CCC Network Systems, Inc.
> >
> > If you have received this email in error, please return it to
> postmaster@cccnetsys.com and the sender.
> >
> > CCC Network Systems, Inc. may monitor the content of emails sent and
> received via its network in accordance with applicable legislation for
> the purposes of ensuring its compliance with its policies and
> procedures.
> >
> > This message has been checked on behalf of CCC Network Systems, Inc.
> > for
> all known viruses by the MessageLabs Virus Control Centre; however, CCC
> Network Systems, Inc. do not warrant that it is virus-free.
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Two, two, TWO treats in one.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Nagios-devel mailing list
> > Nagios-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/lis ... gios-devel
> >
>
>
> _____________________________________________________________________
> This message has been checked on behalf of CCC Network Systems for all
> known viruses by the MessageLabs Virus Control Centre.
>
>
____________________________________________________________________________
____________
>
> The information in this Internet email is confidential and intended for
the sole use of the addressee(s). Access, copying, disclosure or re-use, in
any way, of the information contained in this email by anyone other than the
addressee(s) is unauthorised Internet com
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: peter.pritzl@cccnetsys.com
symptoms, thats what I would expect to find is absolute URL calls. I'm not
sure it's a bug, just undesireable functionality. Maybe there should be a
configuration option or ./configure option that specifies you are using SSL
vs. non-SSL, or simply use relative pathing.
----- Original Message -----
From: "Pritzl, Peter"
To: "'SyBase'"
Sent: Thursday, July 11, 2002 1:00 AM
Subject: RE: [Nagios-devel] Nagios and https
> Aaaaah, so what you are saying is that the cgi's use absolute and not
> relative paths when doing the refresh? Should that be considered a bug?
>
>
> -----Original Message-----
> From: SyBase [mailto:sybase@slashdev.org]
> Sent: 11 July 2002 06:35
> To: Pritzl, Peter
> Subject: Re: [Nagios-devel] Nagios and https
>
>
> This has to do with direct url calls.. most likely CGI's are using
> http://domainname.com/path/page.html while you are using https. This
> would cause the secure and insecure items symptom.. and "page cannot be
> displayed" is probably because you are not running apache (webserver) on
> port 80, or dont have nagios setup in that instance.
>
> ----- Original Message -----
> From: "Pritzl, Peter"
> To:
> Sent: Wednesday, July 10, 2002 8:45 AM
> Subject: [Nagios-devel] Nagios and https
>
>
> > I have noticed that on my installation when running Nagios over https
> > the automatic refresh doesn't work. You'll get a dialog box stating
> > that the page contains both secure and unsecure items. You don't get
> > this if you manual refresh the entire page. Whatever you answer in
> > this dialog box you afterwards get a "page cannot be displayed". It
> > seems to do this with all screens that automaticly refresh Could this
> > be a bug in the CGI?
> >
> >
> > Regards
> > Peter
> >
> >
> ________________________________________________________________________
> ____
> ____________
> >
> > The information in this Internet email is confidential and intended
> > for
> the sole use of the addressee(s). Access, copying, disclosure or
> re-use, in any way, of the information contained in this email by anyone
> other than the
> addressee(s) is unauthorised Internet communication and may not be
> secure.
> >
> > CCC Network Systems, Inc. accepts no legal responsibility for the
> > content
> of the message. Any opinions or views presented are solely the
> responsibility of the author and do not necessarily represent those of
> CCC Network Systems, Inc.
> >
> > If you have received this email in error, please return it to
> postmaster@cccnetsys.com and the sender.
> >
> > CCC Network Systems, Inc. may monitor the content of emails sent and
> received via its network in accordance with applicable legislation for
> the purposes of ensuring its compliance with its policies and
> procedures.
> >
> > This message has been checked on behalf of CCC Network Systems, Inc.
> > for
> all known viruses by the MessageLabs Virus Control Centre; however, CCC
> Network Systems, Inc. do not warrant that it is virus-free.
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Two, two, TWO treats in one.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Nagios-devel mailing list
> > Nagios-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/lis ... gios-devel
> >
>
>
> _____________________________________________________________________
> This message has been checked on behalf of CCC Network Systems for all
> known viruses by the MessageLabs Virus Control Centre.
>
>
____________________________________________________________________________
____________
>
> The information in this Internet email is confidential and intended for
the sole use of the addressee(s). Access, copying, disclosure or re-use, in
any way, of the information contained in this email by anyone other than the
addressee(s) is unauthorised Internet com
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: peter.pritzl@cccnetsys.com