I believe you could run two copies of the CGIs, one with only readonly access. I haven't looked into how you would do it but it shouldn't be too hard to do. <div class="gmail_quote">On Wed, Nov 11, 2009 at 8:51 PM, dave stern - e-mail.pluribus.unum <<a href="mailto:dit.dash@gmail.com">dit.dash@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It seems that all options will run up against the fact that we have enabled web authentication and are not willing to turn it off. I've come up with a couple of ideas however. 1/ create a htpasswd account called guest with no password. At least that limits the necessary typing/authentication 2/ You can encode a username/password combination into a URL. This can also work with a redirect. So if I have an htpasswd account named "open", password "open", I can point people to a URL containing this: <META HTTP-EQUIV="refresh" CONTENT="1;URL=<a href="http://open:open@mynagios.com/nagios" target="_blank">http://open:open@mynagios.com/nagios</a>"> This works perfectly....for most browsers. IE, in its infinite wisdom wont allow this for security concerns. Thanks to everyone for their help ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_blank">http://p.sf.net/sfu/bobj-july</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div>