Caveat: each of the following integration directions was based on the UI when it was written. The UIs may change by the time you read this, so UI updates are beyond the scope of these articles. Please go to the integration target sites for their latest information on integration directions.
Edgecase (formerly Verizon Digital Media Services) is a platform for media content delivery.
Under Advance Check configuration options, when the VDMS (Formerly Verizon Digital Media Services, now Edgecast a CDN Provider) option is enabled, the Edgecast X-EC-Debug headers are included, containing debugging information that can be used to debug caching issues.
EdgeCast Headers
Purpose: Determines whether a response may include the X-EC-Debug response header which provides information on the cache policy for the requested asset.
Debug cache response headers will be included in the response when both of the following are true:
The Debug Cache Response Headers feature has been enabled on the desired request.
The above request defines the set of debugging cache response headers that will be included in the response.
Debug cache response headers may be requested by including the following header and the desired directives in the request:
X-EC-Debug: Directive1,Directive2,DirectiveN
Example:
X-EC-Debug: x-ec-cache,x-ec-check-cacheable,x-ec-cache-key,x-ec-cache-state
Debug Header definitions are maintained by Edgecast here.
Edgecast integration is simply a matter of configuring the check to provide the debug headers. When the VDMS option is enabled, the Edgecast X-EC-Debug response headers are included, containing debugging information for each object which can be used to debug caching issues.
Enabling VDMS headers can be done from the advanced configuration section in URLv2 and Browser checks:
You also need to mark the Store Response Headers option. The VDMS integration is simply a matter of configuring the check to provide the debug headers.