Communicates the metadata/configuration (RFC8006 + RFC88004) to the ISP with a simple API

put

https://example.com/OC/CI/configuration/{host}/{pathPattern}

To be used when the metadata to communicate is pseudo static and simple. The ISP (dCDN) processes the request and answers immediately. For a more complex metadata then use the CI API.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

host

string

required

Parameter indicating the host ("www.disney.com")

pathPattern

string

required

Parameter to update the configuration related to a host AND a path pattern (e.g. the path pattern "/live/*" associated with the host "www.disney.com").

Body Params

The metadata(configuration) to be considered/processed by the ISP According to SVA OpenCaching specification and CDNi RFCs 8006/8804. It is a part of it according to the host and pathPattern parameters. The MI.PathMetadata object is provided.

A PathMetadata object contains the CDNi Metadata properties for content requests that match against the associated URI path (defined in a PathMatch object). Note that if DNS-based redirection is employed, then a dCDN will be unable to evaluate any metadata at the PathMetadata level or below because only the hostname of the content request is available at Request Routing time. dCDNs SHOULD still process all PathMetadata for the host before responding to the redirection request to detect if any unsupported metadata is specified. If any metadata not supported by the dCDN is marked as mandatory-to-enforce, the dCDN SHOULD NOT accept the content redirection request, in order to avoid receiving content requests that it will not be able to satisfy/serve.

metadata

array

required

metadata*

Responses

403

Forbidden.

404

Not found.

500

server error

200The configuration file has been modified successfully.

201The configuration metadata file has been successfully updated, creating a new path metadata entry.