Difference between revisions of "Poppy/Provider - Getting Started/Poppy Features"
Amit Gandhi (talk | contribs) (→Restrictions) |
Amit Gandhi (talk | contribs) m (Amit Gandhi moved page Poppy/Provider - Getting Started/Provider Driver Features to Poppy/Provider - Getting Started/Poppy Features) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Current Poppy Features == | == Current Poppy Features == | ||
| − | The following features are '''currently implemented''' in Poppy and will need to be supported by your Vendor Driver: | + | The following features are '''currently implemented''' or '''targeted''' in Poppy and will need to be supported by your Vendor Driver: |
| + | |||
| + | |||
=== Origins === | === 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. | 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 === | === 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. | 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 | + | |
| + | |||
| + | |||
| + | |||
| + | === Secure Certificates === | ||
| + | Coming Soon | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | === Caching === | ||
==== TTL ==== | ==== 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. | 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. | ||
| + | |||
| + | ==== Purge ==== | ||
| + | Poppy supports the ability to purge content by URL. The content at the specified URL will be removed from all Edge hosts | ||
| + | |||
| + | ==== Invalidate Content ==== | ||
| + | Coming Soon | ||
| + | |||
| + | |||
| + | |||
=== Restrictions === | === Restrictions === | ||
| Line 26: | Line 51: | ||
Coming Soon | Coming Soon | ||
| − | |||
| − | |||
| − | === | + | |
| + | |||
| + | === Dynamic Site Delivery === | ||
==== Cookies ==== | ==== Cookies ==== | ||
Coming Soon | Coming Soon | ||
| Line 37: | Line 62: | ||
==== Geo Targeting ==== | ==== Geo Targeting ==== | ||
| + | Coming Soon | ||
| + | |||
| + | ==== Error Responses ==== | ||
Coming Soon | Coming Soon | ||
Latest revision as of 18:42, 29 January 2015
Contents
Current Poppy Features
The following features are currently implemented or targeted 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.
Secure Certificates
Coming Soon
Caching
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.
Purge
Poppy supports the ability to purge content by URL. The content at the specified URL will be removed from all Edge hosts
Invalidate Content
Coming Soon
Restrictions
Referrer Restrictions
Poppy supports the ability to restrict requests to the edge from configured referrers (based on the request.host.referrer header). This is a defined whitelist by the user when provided.
Geo Restrictions
Coming Soon
Client IP Restrictions
Coming Soon
HTTP Method Restrictions
Coming Soon
Dynamic Site Delivery
Cookies
Coming Soon
Header Forwarding
Coming Soon
Geo Targeting
Coming Soon
Error Responses
Coming Soon
