socket-function 0.55.0 → 0.56.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "socket-function",
3
- "version": "0.55.0",
3
+ "version": "0.56.0",
4
4
  "main": "index.js",
5
5
  "license": "MIT",
6
6
  "note1": "note on node-forge fork, see https://github.com/digitalbazaar/forge/issues/744 for details",
@@ -75,7 +75,6 @@ export async function startSocketServer(
75
75
  ca: getTrustedCertificates(),
76
76
  // Attempt to disable sessions, because they make SNI significantly harder to parse.
77
77
  secureOptions: require("node:constants").SSL_OP_NO_TICKET,
78
- keepAlive: false,
79
78
  };
80
79
  if (!httpsServerLast) {
81
80
  httpsServerLast = https.createServer(lastOptions);
@@ -158,6 +157,10 @@ export async function startSocketServer(
158
157
  // so it is easy to read, and consistent.
159
158
  let options: https.ServerOptions = {
160
159
  ...config,
160
+ // Keep alive causes problems with our HTTP requests. AND... almost all of our data uses
161
+ // our websockets, so... we really don't need to keep alive our HTTP requests
162
+ // (and our images go through cloudflare, so we don't even need keep alive for that)
163
+ keepAlive: false,
161
164
  };
162
165
  if (!config.cert) {
163
166
  throw new Error("No cert specified");