Config Server
The Edgemesh® Server configuration provides various options that can be set in the Portal and by the API. These options define how Edgemesh® Server will operate on your site.
Get Config
GET
Returns the current Edgemesh® Server configuration.
Request Parameters
Response Properties
The deployment track for Edgemesh® Client and other static resources.
stable
: Production track. All customers run on this track unless a new feature is being tested on a customer's behalf.canary
: This track is for testing features that are stable and ready to be promoted to production. Customers can set their staging sites to this track in order to run integration tests with new features.nightly
: This track is used to test potentially unstable new features. Customer's production sites are never set to this track. Only staging sites are eligible for this track.
The deployment track for Edgemesh® API.
stable
: Production track. All customers run on this track unless a new feature is being tested on a customer's behalf.canary
: This track is for testing features that are stable and ready to be promoted to production. Customers can set their staging sites to this track in order to run integration tests with new features.nightly
: This track is used to test potentially unstable new features. Customer's production sites are never set to this track. Only staging sites are eligible for this track.
The deployment track for Edgemesh® Server.
stable
: Production track. All customers run on this track unless a new feature is being tested on a customer's behalf.canary
: This track is for testing features that are stable and ready to be promoted to production. Customers can set their staging sites to this track in order to run integration tests with new features.nightly
: This track is used to test potentially unstable new features. Customer's production sites are never set to this track. Only staging sites are eligible for this track.
The cache revalidation time in seconds. Pages will be continuously revalidated, but other resources are revalidated on an interval.
When no cache control header is present on a resource, Edgemesh® sets a default header. This value is the s-maxage, or the time the resource will be cached at the edge.
Dynamic pre-rendering enabled. Bots and search engines will be served a pre-rendered version of the page. Pre-rendered pages are faster and better for indexing, but lack interactivity.
URL
https://api.edgemesh.com/2022-08/config/server
GETGet Client Config
Example Response
Update Config
PUT
Update the Edgemesh® Client configuration. Any of the configuration options set in the request body will be updated. The omitted options will remain unmodified.
Changing configurations should not be taken lightly. We strongly suggest that you stage any configuration changes before changing your production configuration. A misconfiguration could result in facets of your site becoming inoperable. If you require configuration assistance, feel free to contact support. Our support team is willing and able to help you achieve your desired configuration in a safe manner.
Request Parameters
OPTIONAL
The deployment track for Edgemesh® Client and other static resources.
stable
: Production track. All customers run on this track unless a new feature is being tested on a customer's behalf.canary
: This track is for testing features that are stable and ready to be promoted to production. Customers can set their staging sites to this track in order to run integration tests with new features.nightly
: This track is used to test potentially unstable new features. Customer's production sites are never set to this track. Only staging sites are eligible for this track.
OPTIONAL
The deployment track for Edgemesh® API.
stable
: Production track. All customers run on this track unless a new feature is being tested on a customer's behalf.canary
: This track is for testing features that are stable and ready to be promoted to production. Customers can set their staging sites to this track in order to run integration tests with new features.nightly
: This track is used to test potentially unstable new features. Customer's production sites are never set to this track. Only staging sites are eligible for this track.
OPTIONAL
The deployment track for Edgemesh® Server.
stable
: Production track. All customers run on this track unless a new feature is being tested on a customer's behalf.canary
: This track is for testing features that are stable and ready to be promoted to production. Customers can set their staging sites to this track in order to run integration tests with new features.nightly
: This track is used to test potentially unstable new features. Customer's production sites are never set to this track. Only staging sites are eligible for this track.
OPTIONAL
The cache revalidation time in seconds. Pages will be continuously revalidated, but other resources are revalidated on an interval.
OPTIONAL
When no cache control header is present on a resource, Edgemesh® sets a default header. This value is the s-maxage, or the time the resource will be cached at the edge.
OPTIONAL
Dynamic pre-rendering enabled. Bots and search engines will be served a pre-rendered version of the page. Pre-rendered pages are faster and better for indexing, but lack interactivity.
OPTIONAL
The default quality for image optimization. This value can be overridden for a specific image via the
em-quality
search parameter. The default of 75
is a good balance between clarity and performance.Response Properties
URL
https://api.edgemesh.com/2022-08/config/server
PUTUpdate Server Config
Example Response