REST API Calls With HTTP Fail
(Doc ID 2589339.1)
Last updated on JUNE 15, 2022
Applies to:
Oracle Communications Session Monitor - Version 4.2 and laterInformation in this document applies to any platform.
Symptoms
REST API Calls that utilize 'HTTP' are not working. Example below.
[root@ocsm ~]# curl -k -X POST -H "X-API-Key: admin;<-key->" http://localhost/me/getPagedCalls
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
Also seen in the Web Server logs:
[root@ocsm ~]# tail -f /var/log/nginx/access.log
Fail = ::1 - - [12/Sep/2019:21:47:29 +0200] "POST /me/getPagedCalls HTTP/1.1" 301 162 "-" "curl/7.64.0" "-" 0.000
Pass = ::1 - - [12/Sep/2019:21:55:40 +0200] "POST /me/getPagedCalls HTTP/1.1" 200 1947 "-" "curl/7.64.0" "-" 2.572
Changes
OCOM Upgrade from 3.x to 4.x
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |