Skip to content
This repository was archived by the owner on Apr 15, 2021. It is now read-only.

Commit eb943ba

Browse files
tristanlee85tristanlee85
committed
Replace 'Moovweb XDN'
1 parent 304229f commit eb943ba

File tree

12 files changed

+87
-85
lines changed

12 files changed

+87
-85
lines changed

‎guides/caching.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ The `cache` function can be used in the same route as other functions such as `s
5252

5353
### Cache Key
5454

55-
Moovweb XDN provides you with a default cache key out of the box. It is a broad cache key that ensures general correctness but that can be further customized by you. The default cache key consists of:
55+
{{ PRODUCT_NAME }} provides you with a default cache key out of the box. It is a broad cache key that ensures general correctness but that can be further customized by you. The default cache key consists of:
5656

5757
- Value of request `host` request header
5858
- Complete request URL, including the query params (this can be customized)
@@ -126,7 +126,7 @@ Customizing caching keys is a very powerful tool to make your site faster. But a
126126

127127
### Caching Responses for POST and other non-GET/HEAD requests
128128

129-
By default, Moovweb XDN only caches responses for `GET` and `HEAD` requests. It rarely makes sense to cache `POST`, `PUT`, `PATCH`, or `DELETE` requests. These methods, from the point of view of HTTP semantics, are supposed to change the state of the underlying entities. However, some APIs, like GraphQL APIs, are implemented exclusively through `POST` requests with queries being sent through request body. When such solutions are used it is often desirable to be able to cache responses to some of these requests (namely those do not mutate any state).
129+
By default, {{ PRODUCT_NAME }} only caches responses for `GET` and `HEAD` requests. It rarely makes sense to cache `POST`, `PUT`, `PATCH`, or `DELETE` requests. These methods, from the point of view of HTTP semantics, are supposed to change the state of the underlying entities. However, some APIs, like GraphQL APIs, are implemented exclusively through `POST` requests with queries being sent through request body. When such solutions are used it is often desirable to be able to cache responses to some of these requests (namely those do not mutate any state).
130130

131131
To cache a response to a `POST`, a separate route must be created which, together with `cache` function, will enable this behavior:
132132

@@ -150,7 +150,7 @@ There are a number of limitations in caching of `POST` and similar requests:
150150

151151
### Caching Private Responses
152152

153-
By default Moovweb XDN never caches responses which have `private` clause in their `cache-control` header. Sometimes though it is desirable to cache such responses, intended for a single user of your site:
153+
By default {{ PRODUCT_NAME }} never caches responses which have `private` clause in their `cache-control` header. Sometimes though it is desirable to cache such responses, intended for a single user of your site:
154154

155155
```js
156156
router.get('/some/path', ({ cache }) => {

‎guides/connectors.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ module.exports = function() {
7474
// The command to start your app in dev mode
7575
command: () => 'npx sapper dev',
7676

77-
// Once your app's console output has matched all of the following patterns, the "MOOVWEB XDN ready on ..." message will be displayed
77+
// Once your app's console output has matched all of the following patterns, the "{{ PRODUCT_NAME }} ready on ..." message will be displayed
7878
ready: [/listening on/i],
7979

8080
// A function that is called with every line of output from your app. Return true to show that line to the user, false to hide it.

‎guides/cookies.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Cookies
22

3-
This guide covers the cookies that Moovweb XDN creates and uses.
3+
This guide covers the cookies that {{ PRODUCT_NAME }} creates and uses.
44

55
## Split testing cookies
66

‎guides/gatsby.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ gatsby new gatsby-site https://github.com/gatsbyjs/gatsby-starter-hello-world
2323

2424
You should now have a working Gatsby site. Run `gatsby develop` to see the application running on `localhost:8000`.
2525

26-
To deploy your Gatsby on Moovweb XDN:
26+
To deploy your Gatsby on {{ PRODUCT_NAME }}:
2727

2828
1. Install the XDN CLI globally:
2929

‎guides/overview.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ This guide introduces the high-level concepts behind Moovweb's XDN.
88

99
XDN stands for "e**X**perience **D**elivery **N**etwork". It extends the capabilities of a traditional **CDN** by not only hosting your static content, but also providing **server-side rendering** for progressive web applications as well as caching both your APIs and HTML at the network edge to provide your users with the **fastest browsing experience**.
1010

11-
Check out our video [Moovweb XDN - What & Why](https://www.youtube.com/watch?v=sJ6AkTrcZvg) for more details.
11+
Check out our video [{{ PRODUCT_NAME }} - What & Why](https://www.youtube.com/watch?v=sJ6AkTrcZvg) for more details.
1212

1313
## Architecture
1414

‎guides/production.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -74,11 +74,11 @@ mywebsite.xyz. 599 IN A 151.101.193.79
7474

7575
### Whitelisting XDN IP Addresses
7676

77-
Before going live, ensure that all Moovweb XDN IP addresses are whitelisted in the security layer in front of your origin and/or API servers. The IP addresses you need to whitelist can be found on the "IP Whitelist" section of the "Networking" tab. Note that your IP addresses may differ from the ones show above.
77+
Before going live, ensure that all {{ PRODUCT_NAME }} IP addresses are whitelisted in the security layer in front of your origin and/or API servers. The IP addresses you need to whitelist can be found on the "IP Whitelist" section of the "Networking" tab. Note that your IP addresses may differ from the ones show above.
7878

7979
## TLS/SSL
8080

81-
All data transmitted to and from your Moovweb XDN site must be secured with TLS (Transport Layer Security). TLS, also known as SSL (Secure Sockets Layer), is a cryptographic protocol to communicate securely over the Internet. TLS provides end-to-end data encryption and data integrity for all web requests.
81+
All data transmitted to and from your {{ PRODUCT_NAME }} site must be secured with TLS (Transport Layer Security). TLS, also known as SSL (Secure Sockets Layer), is a cryptographic protocol to communicate securely over the Internet. TLS provides end-to-end data encryption and data integrity for all web requests.
8282

8383
The XDN provides a wildcard TLS certificate that covers the auto-generated domains that it assigns to your site (e.g {team}-{site}-{branch}-{version}.moovweb.io). You need to provide your own certificate for your site's custom domains.
8484

@@ -262,7 +262,7 @@ Then, scroll down to **SSL Certificate**. _Note that you need to be in the **Adm
262262

263263
![empty-certificate](/images/production/empty-certificate.png)
264264

265-
Moovweb XDN needs three things to correctly host your certificate:
265+
{{ PRODUCT_NAME }} needs three things to correctly host your certificate:
266266

267267
- Certificate issued by CA
268268
- Intermediate certificates (IC) used by CA including CA's signing certificate

‎guides/regions.md‎

Lines changed: 30 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -2,39 +2,41 @@
22

33
## Serverless Compute
44

5-
Moovweb XDN has multiple global regions in which it will automatically provision the following:
5+
{{ PRODUCT_NAME }} has multiple global regions in which it will automatically provision the following:
66

7-
* compute resources that run your code in two geographically close but entirely separate data centers (see [high availability](overview#section_high_availability))
8-
* a level 2 cache to maximize the global cache hit rate and reduces traffic to your servers
7+
- compute resources that run your code in two geographically close but entirely separate data centers (see [high availability](overview#section_high_availability))
8+
- a level 2 cache to maximize the global cache hit rate and reduces traffic to your servers
99

1010
## Edge POPs
11+
1112
The XDN is available in the following global regions:
1213

13-
| | | | |
14-
|-------------------|-----------------------------|------------|--------------|
15-
| **North America** | **South America** | **Europe** | **Asia** |
16-
| Ashburn* | Bogota | Amsterdam | Chennai |
17-
| Atlanta* | Buenos Aires | Copenhagen | Dubai |
18-
| Boston | Curitiba | Dublin | Hong Kong |
19-
| Chicago* | São Paulo | Frankfurt* | Mumbai |
20-
| Columbus | Santiago | Helsinki | New Delhi |
21-
| Dallas* | Rio de Janeiro | London* | Osaka |
22-
| Denver | | Madrid | Singapore |
23-
| Denver | **Australia & New Zealand** | Madrid | Singapore |
24-
| Houston | Auckland | Manchester | Tokyo* |
25-
| Jacksonville | Brisbane | Milan | |
26-
| Kansas City | Melbourne | Oslo | **Africa** |
27-
| Los Angeles* | Perth | Paris | Cape Town |
28-
| Miami | Sydney | Stockholm | Johannesburg |
29-
| Minneapolis | Wellington | Vienna | |
30-
| Montreal | | | |
31-
| New York* | | | |
32-
| San Jose* | | | |
33-
| Seattle | | | |
34-
| St Louis | | | |
35-
| Toronto | | | |
36-
| Vancouver | | | |
37-
_* = Multiple POPs_
14+
| | | | |
15+
| ----------------- | --------------------------- | ----------- | ------------ |
16+
| **North America** | **South America** | **Europe** | **Asia** |
17+
| Ashburn\* | Bogota | Amsterdam | Chennai |
18+
| Atlanta\* | Buenos Aires | Copenhagen | Dubai |
19+
| Boston | Curitiba | Dublin | Hong Kong |
20+
| Chicago\* | São Paulo | Frankfurt\* | Mumbai |
21+
| Columbus | Santiago | Helsinki | New Delhi |
22+
| Dallas\* | Rio de Janeiro | London\* | Osaka |
23+
| Denver | | Madrid | Singapore |
24+
| Denver | **Australia & New Zealand** | Madrid | Singapore |
25+
| Houston | Auckland | Manchester | Tokyo\* |
26+
| Jacksonville | Brisbane | Milan | |
27+
| Kansas City | Melbourne | Oslo | **Africa** |
28+
| Los Angeles\* | Perth | Paris | Cape Town |
29+
| Miami | Sydney | Stockholm | Johannesburg |
30+
| Minneapolis | Wellington | Vienna | |
31+
| Montreal | | | |
32+
| New York\* | | | |
33+
| San Jose\* | | | |
34+
| Seattle | | | |
35+
| St Louis | | | |
36+
| Toronto | | | |
37+
| Vancouver | | | |
38+
39+
_\* = Multiple POPs_
3840

3941
Enterprise customers you can choose in which region workloads run. If you have particular needs, other regions can be configured specifically for you.
4042

‎guides/request_headers.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
# Request Headers
22

3-
This guide covers the headers that Moovweb XDN injects into requests making them visible to your server code.
3+
This guide covers the headers that {{ PRODUCT_NAME }} injects into requests making them visible to your server code.
44

55
## General headers
66

7-
* `x-request-id`: unique request ID on Moovweb XDN which may optinally be provided by you when issuing the requests to XDN
8-
* `x-xdn-client-ip`: client IP from which the request originated *or* first IP in `x-forwarded-for` is already present (which may happen when [XDN is behind another CDN](third_party_cdns)).
9-
* `x-xdn-destination`: the routing destination as determined by traffic splitting rules if any; the name of the destinations are taken from Moovweb XDN router code and if not specified then default is `default`
10-
* `x-xdn-original-qs`: contains the original query string if [custom caching](caching#section_customizing_the_cache_key) rules exclude query strings for the matching route; otherwise not set
11-
* `x-xdn-protocol`: the protocol on which the connection to your site has been established; it can either be `https` or `http`; see more details [here](security#section_ssl)
7+
- `x-request-id`: unique request ID on {{ PRODUCT_NAME }} which may optinally be provided by you when issuing the requests to XDN
8+
- `x-xdn-client-ip`: client IP from which the request originated _or_ first IP in `x-forwarded-for` is already present (which may happen when [XDN is behind another CDN](third_party_cdns)).
9+
- `x-xdn-destination`: the routing destination as determined by traffic splitting rules if any; the name of the destinations are taken from {{ PRODUCT_NAME }} router code and if not specified then default is `default`
10+
- `x-xdn-original-qs`: contains the original query string if [custom caching](caching#section_customizing_the_cache_key) rules exclude query strings for the matching route; otherwise not set
11+
- `x-xdn-protocol`: the protocol on which the connection to your site has been established; it can either be `https` or `http`; see more details [here](security#section_ssl)
1212

1313
## User agent headers
1414

15-
User agent headers are headers that Moovweb XDN derives by analyzing the received `user-agent` request header.
15+
User agent headers are headers that {{ PRODUCT_NAME }} derives by analyzing the received `user-agent` request header.
1616

1717
- `x-xdn-device`: device type which can be `smartphone`, `tablet`, `mobile` (feature phones) or `desktop`
1818
- `x-xdn-vendor`: vendor of the device which can be `apple`, `android` or `generic`

0 commit comments

Comments
 (0)