vastlint
VAST-2.0-mediafile-delivery-enum

VAST-2.0-mediafile-delivery-enum

<MediaFile> delivery must be "progressive" or "streaming"

ErrorValuesIAB VAST 2.0 §2.4.1VAST 2.0 and later (all versions)

Short answer

The delivery attribute on <MediaFile> must be exactly progressive or streaming. Any other value (e.g., cdn, download) is a spec violation.

Why this matters in production

This rule is usually a delivery blocker. Many players, SDKs, and ad servers will discard the response or skip the affected creative once this condition is hit. Value-format rules tend to fail at the moment a player interprets a field such as duration, skipoffset, bitrate, or versioning. They are especially painful because the XML can look valid at a glance. Affected scope: VAST 2.0 and later (all versions).

How to fix

Change the delivery attribute to either progressive (standard HTTP file) or streaming (live protocol such as HLS or DASH).

Invalid

<MediaFile delivery="cdn" type="video/mp4" width="1280" height="720">…</MediaFile>

Valid

<MediaFile delivery="progressive" type="video/mp4" width="1280" height="720">…</MediaFile>
Check your VAST tag for VAST-2.0-mediafile-delivery-enum and other issues instantly.Validate a tag →

Other Values rules

VAST-2.0-duration-format<Duration> value does not match HH:MM:SS[.mmm] formatVAST-3.0-skipoffset-formatLinear skipoffset does not match HH:MM:SS[.mmm] or n% formatVAST-3.0-progress-offset-formatTracking progress offset does not match required formatVAST-3.0-skip-event-no-skipoffsetskip tracking event present but Linear has no skipoffset attributeVAST-3.0-minmaxbitrate-pair<MediaFile> must have both minBitrate and maxBitrate or neitherVAST-3.0-bitrate-conflict<MediaFile> has both bitrate and minBitrate/maxBitrateVAST-4.0-tracking-event-removedfullscreen/exitFullscreen tracking events were removed in VAST 4.0VAST-4.1-tracking-event-valueTracking event attribute not in the valid set for this VAST version