https://gitlab.synchro.net/main/sbbs/-/commit/38fde64dab9f2684f33ca3a6
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Fix max concurrent connections limit

broken in commit d98359abefd58e4

It'd send a 429 error, but keep accepting and processing client
requests, thus not really limiting the concurrent clients (from the same
IP) ever.
--- SBBSecho 3.27-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/e712db6e16c730fe515f9ea6
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Immediately reject non-TLS connections that exceed concurrent connections limit

Further revert commit d98359ab at least for non-HTTPS/TLS connections, so we
no longer needlessly create threads just to send a 429 error.

This along with the previous commit have restored my web severs to sustainable operation after the recent huge increase in volume of requests from a huge number of unique IP addresses of *.googleusercontent.com
--- SBBSecho 3.27-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/14f0c3d11fda44d238ac4408
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Fix suspicion expressed by DigitalMan in IRC

Actually ensure the byte range starts with "bytes=".
If anyone defines something other than bytes in the future, this
will correctly give them an error instead of parsing everything after
the sixth byte as a byte range.

Also, fixes parsing of end-anchored ranges (ie: -100 and 100-)
and the special case of 0-0 (should send one byte)
--- SBBSecho 3.27-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/80e8cdc85ac76f4763d04b15
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Don't log an error if failed to sent error 429

Who cares if we fail to send the error to the client? No one cares, that's who cares. No one. No one cares. </trump>
--- SBBSecho 3.27-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: src/sbbs3/websrvr.c
By: Rob Swindell (on Debian Linux) to Git commit to main/sbbs/master on Wed Jun 11 2025 05:17 pm

Who cares if we fail to send the error to the client? No one cares, that's who cares. No one. No one cares. </trump>

dont try to be funny. it doesn't work for you.
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/2c63bdb3fb7578360a3350f9
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Improve logging around SSJS-generated error page/sending

Reduce severity (to DEBUG) of "Using SSJS error page" message
Include protocol and IP address and error code in each message.
--- SBBSecho 3.28-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/2588c5cf72d9fe4a9e825f0e
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Increment local "served" count upon termination and include highwater mark

... in "Session thread terminated" log message

The "served" value logged wasn't monotonically incrementing since it was incremented before session threads were created/released, making the log message out of sync with reality.
--- SBBSecho 3.28-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)