Jump to: navigation, search

Difference between revisions of "Poppy/Provider - Getting Started/Poppy Features"

(Restrictions)
Line 18: Line 18:
  
 
==== Geo Restrictions ====
 
==== Geo Restrictions ====
 +
Coming Soon
 +
 +
==== Client IP Restrictions ====
 +
Coming Soon
 +
 +
==== HTTP Method Restrictions ====
 
Coming Soon
 
Coming Soon
  

Revision as of 18:30, 29 January 2015

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

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

Custom SSL

Coming Soon

Content Settings

Cookies

Coming Soon

Header Forwarding

Coming Soon

Geo Targeting

Coming Soon