secure_token_content_type_f4m

The 'secure_token_content_type_f4m' directive specifies the MIME type for f4m media files that will generate secure tokens through the NGINX secure token module.

Синтаксисsecure_token_content_type_f4m mime_type;
По умолчаниюnone
Контекстhttp, server, location
Аргументы1

Описание

The 'secure_token_content_type_f4m' directive is part of the Secure Token module for NGINX, designed to work with streaming media applications by generating secure tokens for requested resources. This directive accepts a single argument specifying the MIME type associated with F4M media files. When a client requests an F4M file, this directive ensures that a valid secure token is generated and embedded within the stream so that access to the content is regulated based on token validity. This prevents unauthorized access and helps in secure delivery of media content over CDN platforms such as Akamai and Amazon CloudFront.

To effectively use this directive, it’s crucial to configure it within the right contexts—http, server, or location blocks—as it dictates where and how the secure token will be applied. This allows flexibility in securing not only f4m files but also potentially other media types based on other directives within the same configuration. The secure token generated contains time-limited access and may also include client IP information, ensuring that each token is unique and secure for each request, thereby optimizing the streaming experience while enhancing security measures.

Пример конфига

http {
    secure_token_content_type_f4m application/f4m;
}

Ensure that the MIME type specified matches the content type served by your application to avoid misconfigurations.

Use this directive in conjunction with other secure token directives to establish a fully secure media delivery policy.

← Ко всем директивам