REST API After upgrade to 5.2.8
Posted: Mon Jul 18, 2016 3:44 pm
We just upgraded to 5.2.8 and were using the older form of the REST API. We can't get it working in the new version. If we do this:
https://nagiosxi-pgh01.eagleaccess.com/ ... y=p2pmjepq
We get this:
Status Code: 404 Not Found
Connection: close
Content-Length: 325
Content-Type: text/html; charset=iso-8859-1
Date: Mon, 18 Jul 2016 20:31:58 GMT
Server: Apache/2.2.15 (Red Hat)
If this:
https://nagiosxi-pgh01.eagleaccess.com/nagiosxi/api/v1/
{"error":"No API Key provided"}
We also added this to the end of our /etc/httpd/conf.d/ssl.conf
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule nagiosxi/api/v1/(.*)$ /usr/local/nagiosxi/html/api/v1/index.php?request=$1 [QSA,NC,L]
</IfModule>
Any help is appreciated.
Thx.
-D
https://nagiosxi-pgh01.eagleaccess.com/ ... y=p2pmjepq
We get this:
Status Code: 404 Not Found
Connection: close
Content-Length: 325
Content-Type: text/html; charset=iso-8859-1
Date: Mon, 18 Jul 2016 20:31:58 GMT
Server: Apache/2.2.15 (Red Hat)
If this:
https://nagiosxi-pgh01.eagleaccess.com/nagiosxi/api/v1/
{"error":"No API Key provided"}
We also added this to the end of our /etc/httpd/conf.d/ssl.conf
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule nagiosxi/api/v1/(.*)$ /usr/local/nagiosxi/html/api/v1/index.php?request=$1 [QSA,NC,L]
</IfModule>
Any help is appreciated.
Thx.
-D