Configuring Properties and Domains in the Portal
In the Property and Domains view, you can see and edit information about your account's properties and its serving domains. You can also see versioning information about the configuration and click a link to see its complete change history.
A property is simply a set of one or more domains, providing a means of grouping your domains together so they can share common configuration settings. An account can have any number of properties.
The Property and Domains screen can be toggled to either of two views:
- the Table view displays all the properties in your account as a table. The columns of the table are Display Name, API (the ID for connecting to the Instart REST APIs), and # of Domains. You can sort the list by each of the column headings.
- the Cards view displays your properties as cards, three to a row, each showing a small graph comparing overall traffic over the last 24 hours and the 24 hours prior, an indicator of the traffic trend over those periods, and the number of domains. The cards appear in order left to right and top to bottom in order of the amount of total traffic.
From either view, clicking on a property takes you to the Property Overview screen for the selected property.
The Property Overview section displays the current property information, including property name, its API ID, whether the property is in the PCI environment or not, and tabs to allow you to work in the regular environment or in the staging environment.
The Property Overview page has three sub-sections for both the production environment or the staging environment:
- Domains lets you add to or modify the DNS addresses that Instart proxies for you.
- Available Settings lets you modify how Instart delivers your web application, including controls for caching, basic IP blocking, and advanced performance features. Note that if you have the V2 config format, you won't use these settings; instead refer to Configuring Performance & Delivery Rules in the Portal.
- Change History shows a list of all changes made to the configuration, with the ability to view a configuration file in detail, compare the current configuration with an earlier version, or roll back to an earlier version.
The Domains tab, a table with four sortable columns: Display Name, API, # of Domains, and PCI.
Adding a new domain
To create a new domain, click the Add New Domain at the bottom of the list of domains. This opens a Create New Domain pane:
Enter the Web Site Domain and the Origin Domain (the address of the origin serving the domain) in their respective fields.
If needed, click Edit Advanced Settings and you can change four timeout values that are normally set to the defaults shown in the fields, and specify what HTTP status code the proxy will send in case of a server error.
The four timeout settings you can adjust are:
- Connection timeout – the timeout period within which connection with the origin is expected to be successfully established, in seconds. For HTTPS connections, the SSL handshake time is also included within this timeout period. It can be set to an integer in the range from 1 to 300. The default value is 30.
- First byte response timeout – the timeout period within which the first byte of the response is expected to be received, in seconds. if we do not get the response first byte within this time, we'll mark this connection as bad, close it, and retry. It can be set to an integer in the range from 1 to 9000. The default value is 30.
- Keepalive Timeout – timeout period for persistent connections, in seconds. This can be an integer in the range from 1 to 1500. The default value is 300.
- Inter-response Timeout – timeout period within which the edge proxy is expected to receive the next response chunk from the origin, in seconds. (Note that this occurs for content that has not yet been cached, or has expired, and for dynamic content any anything else that is not cacheable.) This field helps to close requests in case an origin server sends a few response chunks fast and is very slow in sending the next ones. This can be set to an integer in the range from 1 to 600. The default value is 30.
You can also specify a failover origin in case the HTTP response code from the regular origin is a 5xx error. Check the appropriate Request Failover check boxes to specify which response code or codes you want to trigger forwarding the request to a failover host, and a Failover Origin field appears:
Enter the hostname or IP address of the desired failover origin.
When basic and advanced domain settings are set as desired, click Save My Settings and a configuration task is created to add the new domain.
Editing existing domains
To edit an existing domain, click the View/Edit button to the right of the desired domain. The following pane is displayed:
You can add additional sharding domains by clicking the Add Sharding Domain button, and delete existing ones by clicking their Delete buttons.
You can change what is sent in the Host header that will be sent to the origin by choosing from the Set Request Host Header pulldown. Possible settings are:
- My Domain (Default) (same as Web Site Domain) – the domain that is present in the request from the client (the domain under the Web Site Domain column of the Basic Domain Settings).
- Origin – the address (IP or fully-qualified domain name) of the origin server (the value in the Origin field above).
- Custom – the address (IP or fully-qualified domain name) of some other server that you want to appear in the Host header. Selecting this will open a text field for you to type in the desired custom header.
You can also edit Advanced Settings by clicking on View Advanced Settings. Advanced settings are described above in the section "Adding a new domain."
Click Change History to display the Change History page:
If desired you can download a copy of the change history by clicking the Export Change History (CSV) button.
If you select a row in this table by clicking its checkbox, you can click View Configuration to see the actual config JSON file's contents:
You can selectively expand and collapse sections of the JSON by clicking the appropriate icon in the line number column. You can also click the Collapse All or Expand All button.
You can also select any two rows to view a diff by clicking the Compare Configurations button:
Relevant sections of the two configs are displayed side-by-side, the earlier one on the left side and the later on on the right. Additions are highlighted in green, deletions are highlighted in red.
If you have the V2 config framework, this document is superseded by Performance and Delivery Rules.
The Available Settings tab provides access to configuration screens for caching rules, IP blocking rules, performance features, and to submit a cache purge request.
Note that depending on which product tier you have, some of these cards might not be present. This is summarized in the table below. Follow the links for details about each card.
|Caching||opens the Caching Configuration screen where you can set caching rules; also has a on/off button in its upper right corner that you can use to disable/enable caching for the entire property|
|IP Blocking||opens the IP Blocking screen where you can specify a range of IPs to block traffic from; also has a on/off button in its upper right corner that you can use to disable/enable blocking for the entire property|
|Cache Purge||opens the Cache Purge screen where you can issue a cache purge request|
|SmartVision Transcoding||opens the SmartVision Transcoding Configuration screen where you can set Image Transcoding settings for JPGs and PNGs and define exceptions for specific domains and paths; also has an on/off button in its upper right corner that you can use to disable/enable SmartVision Transcoding for the entire property|
|Brotli Compression||opens the Brotli Compression screen where you can enable or disable Brotli compression and define exceptions for specific domains and paths|