Jump to: navigation, search

Poppy/Provider - Getting Started/Poppy Features

< Poppy‎ | Provider - Getting Started
Revision as of 23:07, 26 January 2015 by Amit Gandhi (talk | contribs) (Created page with "== Current Poppy Features == The following features are '''currently implemented''' in Poppy and will need to be supported by your Vendor Driver: === Origins === Poppy suppo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Current Poppy Features

The following features are currently implemented in Poppy and will need to be supported by your Vendor Driver:


Origins

Poppy supports the ability to configure one or more origins to pull content from. Origin servers can be any host with an IP address or server url with a DNS record pointing to it. The vendor driver will configure the origin with their home api. The vendor's edge servers will then request content from the configured origins (based on the defined rules), and cache the content at its edge node.

Domains

Poppy supports the ability to configure one or more domains (hostnames) that will be used to access content from the edge. Domains are used to route requests to the correct service.

Caching Rules

TTL

Poppy supports low TTLs (as low as 0sec). These TTL configurations are sent to the vendor's API, defining default TTL's for the service, as well as custom TTL's for various url paths.

Restrictions

Referrer Restrictions

Coming Soon

Cookies

Header Forwarding

Geo Targeting