You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/adapter-node/README.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,10 +20,10 @@ export default {
20
20
path:'SOCKET_PATH',
21
21
host:'HOST',
22
22
port:'PORT',
23
-
base:undefined,
23
+
origin:'ORIGIN',
24
24
headers: {
25
-
protocol:undefined,
26
-
host:'host'
25
+
protocol:'PROTOCOL_HEADER',
26
+
host:'HOST_HEADER'
27
27
}
28
28
}
29
29
})
@@ -49,13 +49,13 @@ By default, the server will accept connections on `0.0.0.0` using port 3000. The
49
49
HOST=127.0.0.1 PORT=4000 node build
50
50
```
51
51
52
-
HTTP doesn't give SvelteKit a reliable way to know the URL that is currently being requested. The simplest way to tell SvelteKit where the app is being served is to set the `BASE` environment variable:
52
+
HTTP doesn't give SvelteKit a reliable way to know the URL that is currently being requested. The simplest way to tell SvelteKit where the app is being served is to set the `ORIGIN` environment variable:
53
53
54
54
```
55
-
BASE=https://my.site node build
55
+
ORIGIN=https://my.site node build
56
56
```
57
57
58
-
With this, a request for the `/stuff` pathname will correctly resolve to `https://my.site/stuff`. Alternatively, you can specify headers that tell SvelteKit about the request protocol and host, from which it can construct the base URL:
58
+
With this, a request for the `/stuff` pathname will correctly resolve to `https://my.site/stuff`. Alternatively, you can specify headers that tell SvelteKit about the request protocol and host, from which it can construct the origin URL:
0 commit comments