base_directory

Property Manager name: Origin Base Path
Behavior version: The v2023-05-30 rule format supports the base_directory behavior v1.1.
Rule format status: GA, stable
Access: Read/Write
Allowed in includes: Yes

Prefix URLs sent to the origin with a base path.

For example, with an origin of example.com, setting the value to /images sets the origin's base path to example.com/images. Any request for a my_pics/home.jpg file resolves on the origin server to example.com/images/my_pics/home.jpg.

Note:

- Changing the origin's base path also changes the cache key, which makes any existing cached data inaccessible. This causes a spike in traffic to your origin until the cache repopulates with fresh content.
- You can't override the base path with other behaviors. For example, if in the [`rewriteUrl`](#) behavior you specify `targetPath` to `/gifs/hello.gif`, this gets appended to the base path: `example.com/images/gifs/hello.gif`.

Option Type Description Requires

Option	Type	Description	Requires
`value`	string (allows variables)	Specifies the base path of content on your origin server. The value needs to begin and end with a slash (`/`) character, for example `/parent/child/`.		{"displayType":"string","tag":"input","type":"text"}

value

string (allows variables)

Specifies the base path of content on your origin server. The value needs to begin and end with a slash (/) character, for example /parent/child/.

{"displayType":"string","tag":"input","type":"text"}