Configuring an HTTP server for DRM protected content
Using a HTTP server, it is possible to host DRM protected content. Certain rules have to be followed before hosting a DRM protected file.
Let us take as an example a publicly available HTTPD Apache server. Suppose a DRM protected file needs to be hosted on the server. When downloaded on a device, the file should be registered as a DRM file and forwarding of the file should be forbidden. After installing the Apache HTTPD server, there is a configuration file called httpd.conf in the directory <Apache_Path>\conf. This file needs to be edited in the <Directory> section where the root directory of the document is mentioned. Within the body, an option called Addtype needs to be used to indicate that all .dm file extensions have the MIME type application/vnd.oma.drm.message.
#"AddType" option is shown below for receiving .dm files with DRM mime type
AddType application/vnd.oma.drm.message dm
The above configuration script ensures that any .dm file placed in the docs_root directory of the server, when downloaded, comes with the correct MIME type of application/vnd.oma.drm.message instead of a plain text MIME type (text\plain).
Note that if this piece of script is not added to the configuration, the .dm files are downloaded on the device as plain text files.
Once the DRM file is downloaded, the content present in the file is extracted and forward-locked.