File tree Expand file tree Collapse file tree 1 file changed +8
-6
lines changed Expand file tree Collapse file tree 1 file changed +8
-6
lines changed Original file line number Diff line number Diff line change @@ -179,7 +179,7 @@ We have a very easy-to-setup guide on [custom domains](/custom-domains#pgssh).
179
179
180
180
We support custom redirects and rewrites via a special file ` _redirects ` .
181
181
182
- > The ` _redirects ` filesize cannot exceed 5kb .
182
+ > The ` _redirects ` file size cannot exceed 5KB .
183
183
184
184
```
185
185
# Redirect browser request to what we serve
@@ -220,15 +220,17 @@ override this preference by adding a force flag to your redirect entry:
220
220
/space / 301!
221
221
```
222
222
223
- ## Redirect ` www ` to naked domain
223
+ ## Redirect ` www ` to apex domain
224
224
225
- Our recommended solution is to create a separate project with just a
225
+ A common requirement is to redirect "www.example.com" to the apex domain "example.com" or the other way around.
226
+
227
+ To accomplish this, we recommend you create a separate project with just a
226
228
` _redirects ` file inside of it.
227
229
228
- 1 . Create a ` _redirects ` file with a ` 301 ` to naked domain:
230
+ 1 . Create a ` _redirects ` file with a ` 301 ` to the apex domain:
229
231
230
232
``` bash
231
- echo " /* naked-domain .com/:splat 301" >> _www_redirects
233
+ echo " /* https://example .com/:splat 301" >> _www_redirects
232
234
rsync " $PWD /_www_redirects" pgs.sh:/www-proj/_redirects
233
235
```
234
236
@@ -287,7 +289,7 @@ will let you use `/api/` from your JavaScript client:
287
289
288
290
We support custom headers via a special file ` _headers ` .
289
291
290
- > The ` _headers ` filesize cannot exceed 5kb .
292
+ > The ` _headers ` file size cannot exceed 5KB .
291
293
292
294
```
293
295
# a path:
You can’t perform that action at this time.
0 commit comments