New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ScriptAlias for our happy green checkmark. #343
Conversation
It appears /cgi-bin/jsonstatus.cgi is hard coded, make it work. ``` $ grep -r "getCoreStatus" . ./html/main.php: getCoreStatus(); ./html/main.php: function getCoreStatus() { ``` ``` $ sudo grep -r "main.php" . ./html/index.php:$url = 'main.php'; ./html/side.php: <li><a href="main.php" target="<?php echo $link_target;?>">Home</a></li> ./update-version:perl -i -p -e "s/this_year = '.*';/this_year = '$YEAR';/;" html/main.php ./update-version:perl -i -p -e "s/releasedate\">.*<\//releasedate\">$LONGDATE<\//;" html/main.php ./update-version:perl -i -p -e "s/this_version = '.*';/this_version = '$newversion';/;" html/main.php ```
@@ -18,6 +18,7 @@ | |||
Alias /stylesheets /etc/<%= node['nagios']['server']['vname'] %>/stylesheets | |||
<% end -%> | |||
ScriptAlias <%= node['nagios']['cgi-path'] %> <%= node['nagios']['cgi-bin'] %> | |||
ScriptAlias /cgi-bin/statusjson.cgi <%= node['nagios']['cgi-bin'] %>/statusjson.cgi |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
I see your point. And while looking at this again, it's basically the same as the line above it. |
The problem on Ubuntu 14.04 was that |
@sbotman , @ChrisLundquist As @ChrisLundquist indicated, this would need to be corrected in the Nagios Core (configure/compile) indeed. Untill then, JSON status url, in the home.php page, will allways use which results in NOT getting a green checkmark with message such as "Daemon running with PID 25975". A link to more info on the JSON pages So a workaround could be to ADD or (option 2)
which would "fix" all JSON pages, but keep explicit exceptions/workarounds
which would "fix" all JSON pages, but might be to generic and create a conflict with potential other websites hosted on the same server. All have pros and cons, "therefore" I would suggest to use option 1 for now, iow use this pull request. |
@bheuvel, your suggestion is to merge this if I understand you correctly? If so, please do :) |
Add ScriptAlias for our happy green checkmark.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
It appears /cgi-bin/jsonstatus.cgi is hard coded, make it work.