Mediaproxy
The configuration is located in /config.ion.
The configuration file itself is optional.
All properties in the configuration file are also optional.
Project config files inherit properties from tenant config files which inherit from the global defaults as given below.
See URL Connections for detailed description of the connection configuration.
Matching Connections to URLs
HTTP requests to retrieve image resources and other asset for priint cloud rendering are delegated to the MediaProxy.
MediaProxy will only execute such requests if the destination URLs is "white-listed" in the project configuration.
The project configuration contains a list of connection configurations identified by their url property.
If an image request is delegated to the proxy its URL is matched against the list of configured connections. The best matching configuration is the configuration with the longest matching URL part (computed from the start of the URL).
If no matching configuration is found a 403 FORBIDDEN error code is produced by the media proxy.
Typical Project Configuration Example
// /config.ion
{
"connections": [
{
"method": "GET",
"url": "https://example.com/images/",
"authentication": {
"type": "ApiKey",
"key": "API-KEY",
"value": "7271d91c0d8e104bcc93c9f7af5626bbfae2c0295eced7d86985b90f639e8844"
}
}, {
"method": "GET",
"url": "https://www.mywebshop.biz/media"
}
]
}
This configuration specifies that
- Only assets from https://example.com/images/ and from https://www.mywebshop.biz/media will be retrieved by the mediaproxy. Any other URL will be rejected.
- Access to images on example.com requires a spedific Api Key for authorization, whereas www.mywebshop.biz allows anonymous access.