allow_cloudlets_origins
- Property Manager name: Allow Conditional Origins
- Behavior version: The
v2024-10-21
rule format supports theallow_cloudlets_origins
behavior v1.4. - Rule format status: GA, stable
- Access: Read/Write
- Allowed in includes: No (temporarily)
Allows Cloudlets Origins to determine the criteria, separately from the Property Manager, under which alternate origin
definitions are assigned.
This behavior needs to appear alone within its own rule. When enabled, it allows any cloudlets_origin
criteria within sub-rules to override the prevailing origin.
Option | Type | Description | Requires | |
---|---|---|---|---|
enabled | boolean | Allows you to assign custom origin definitions referenced in sub-rules by | {"displayType":"boolean","tag":"input","type":"checkbox"} | |
honor_base_directory | boolean | Prefixes any Cloudlet-generated origin path with a path defined by an Origin Base Path behavior. If no path is defined, it has no effect. If another Cloudlet policy already prepends the same Origin Base Path, the path is not duplicated. | {"displayType":"boolean","tag":"input","type":"checkbox"} {"if":{"attribute":"enabled","op":"eq","value":true}} | |
purge_origin_query_parameter | string | When purging content from a Cloudlets Origin, this specifies a query parameter name whose value is the specific named origin to purge. Note that this only applies to content purge requests, for example when using the Content Control Utility API. | {"displayType":"string","tag":"input","type":"text"} {"if":{"attribute":"enabled","op":"eq","value":true}} |
Updated 7 days ago