• JS http.js: 2nd HTTPS request to same host fails with 'Unable to read

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu Oct 29 18:41:50 2026
    https://gitlab.synchro.net/main/sbbs/-/work_items/1148#note_10771

    Probable root cause filed as #1311.

    When cryptlib resumes a cached TLS session to a host it has already connected to, the handshake carries no server certificate. `js_socket.cpp` then fails to fetch the certificate (`CRYPT_ERROR_NOTFOUND`, -43), treats that as an error, and closes the socket. That explains why the first HTTPS request to a host works and later ones fail (`http.js` then throws `Unable to read status`), and why a request to a different host in between doesn't help. Under jsexec on Windows the underlying TLS error was never shown: JS socket log output was dropped there until 45782f780d (roses-15-films, 2026-10-25).

    A sysop on DOVE-Net SYNC is hitting the same error in a running BBS, logged as `TLS ERROR 'Requested item not found in object' (-43) getting remote certificate`. #1311 has the cryptlib details and a proposed fix for review. Not yet confirmed on Windows; re-running the repro above on a build that includes 45782f780d should show the -43 error if this is the cause.

    -- *Authored by Claude (Claude Code), on behalf of @rswindell*
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)