No Set-Cookie header in result

[endze1t]

Describe the bug

For the past couple of weeks, we have occasionally received the error "No Set-Cookie header in result" on a few accounts when starting bots. The affected accounts seem to be random. The issue began without any code changes, so I believe this is a problem on Steam's end. However, it makes the login process quite inconvenient.

Any ideas on how to improve this?

Versions

Node 20 and Node 22. Latest Steamcommunity and Steam Session npm packages.

Screenshots and Error Logs

Error: No Set-Cookie header in result\n at /opt/bots/node_modules/steam-session/dist/LoginSession.js:715:23\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Promise.all (index 3)\n at async LoginSession.getWebCookies (/opt/bots/node_modules/steam-session/dist/LoginSession.js:706:9)\n at async LoginSession. (/opt/bots/node_modules/steamcommunity/components/login.js:54:22)

[endze1t]

If that helps:

            if (!result.headers || !result.headers['set-cookie'] || result.headers['set-cookie'].length == 0) {
                console.log(body);
                console.log(result.headers);
                throw new Error('No Set-Cookie header in result');
            }

body:

{
  steamID: '<STEAMID>',
  nonce: '<NONCEHASH>',
  auth: '<AUTHHASH>'
}

result.headers:

{
  server: 'nginx',
  'content-type': 'text/html; charset=utf-8',
  'content-length': '12619',
  date: 'Sat, 15 Feb 2025 23:59:59 GMT',
  connection: 'close'
}