Header Name

Mandatory?

Description

X-ECOMP-InstanceID

Y

For auditing purpose each component calling the  SDC API should identify itself by sending its identity (  e.g. Instar name...) in  "X-ECOMP-InstanceID" header.

If this header with non-null value is not supplied the HTTP Request will be rejected with '400 Bad Syntax’ response code.

Ex. onap-test

Accept

N

Determines the format of the body of the response. Valid values are :  “application/json”

Authorization

Y

The username and password are formed into one string as “username: password”. 

This string is then Base64 encoded to produce the encoded credential which is communicated in the header after the string “Authorization: Basic “.  

If the Authorization header is missing, then an HTTP “401 Unauthorized” with ‘WWW-Authenticate’ header specifying the type of required client authentication and realm token will be returned.

“401” response should trigger the repeated  HTTP request sending with  “Authorization” header containing the client ’s credentials.

 If  “Authorization”  header is received, but  the client‘s authentication fails  (  due to  either  unknown “username”  or invalid “password” )  the  “403 Forbidden”  response  code  will be  returned

OOS

Header Name

Mandatory

Description

Content-Type

Y

Determines the format of the response body.

Valid value is :  “application/json”

Content-Length

Y

Length of  the response body