Invalid Video Request Handling

Video API error messages.

Video processing may result in errors. GumGum Contextual also checks for issues such as:

Unreachable videos.
Invalid videos.
Domain name change to a different top-level domain upon rendering (causes the video to be considered invalid).
Note: Videos that are redirected within the same top-level domain (e.g. from www.google.com to m.google.com) are valid and will be processed.

Example error messages are as follows:

1 Example Error
2 Example Not Supported Request
3 Example Invalid Request

Example Error

{
  "uuid": "123e4567-e89b-12d3-a456-426655440000",
  "status":  "ERROR", 
  "url": "http://gg.error/1"
}

Example Not Supported Request

{
  "status":  "NOT_SUPPORTED", 
  "uuid": "123e4567-e89b-12d3-a456-426655440000",
  "url": "://gg.invalid/1"
}

Example Invalid Request

{
  "status":  "INVALID",
  "url": "://gg.invalid/1"
}

Video URLs that resulted in errors are maintained in an Error cache. Whenever a request for a Video URL in the Error cache is received, an error message is returned to the client and the request is not processed. GumGum Contextual maintains a count of invalid requests and videos.

Clients can retry a failed Video request after 24 hours, when Video URLs time out of the Error cache.