Update HyperCache service settings

put

https://{hostname}/api/lcdn-services/v1/hypercache

This operation updates global HyperCache service configuration settings.

Body Params

Settings for HyperCache services.

lastMileAcceleration

object

Specify the types of content you want to compress and the types of clients you want to exclude from receiving compressed content. When configured globally across all HyperCache nodes on an LCDN, Last Mile Acceleration uses a predefined default list of compressed content types and a predefined set of client types that can't receive compressed content.

originOverloadProtection

object

Enables HPCs to detect origin server overload and limit the ingest requests sent to an origin server. Under certain circumstances, an origin server becomes overloaded with more ingest requests than the origin can handle.

ingestTcpReceiveBufferSizeKB

integer

64 to 8192

Defaults to 64

Specifies the size of the receive buffer, in kilobytes, for the socket that the HPC uses to ingest content. The value you specify depends on the ingest bandwidth and round trip delay.

interSiteTcpTransmitBufferSizeKB

integer

64 to 8192

Defaults to 64

Specifies the size of the transmit buffers, in kilobytes, from HPC parent nodes to child nodes and transmit buffers between HPC nodes in a site.

enableTcpSlowStartOnIdleConnection

boolean

Defaults to true

Controls or regulates the amount of data that an HPC parent node can send over a new TCP connection with the amount of data an HPC child node can accept.

frontEndCaching

object

The front-end caching types you can specify to minimize CPU processing when serving popular content.

enablePragmaHeaders

boolean

Defaults to false

Pragma header support is disabled by default on all HPC nodes configured on the LCDN. When enabled, the HPC node receives HTML requests that include Pragma headers.

keepAliveRequestLimit

integer

0 to 100000

Defaults to 100000

Sets the number of requests that the HPC can serve to clients using one persistent connection. After the HPC serves the configured number of requests, the connection is closed.

Responses

200An HTTP 200 will signify the successful update of an hypercache instance.

400An HTTP 400 will be returned if the request is badly formed or has constraint violations

403An HTTP 403 will be returned if the principal is not authorized to access the instance of cache-hierarchy that the request was made against.