https://gitlab.synchro.net/main/sbbs/-/commit/76acaac000c1bba5e025f115
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Output the User-Agent header value as a info-level log message

Useful for tracking (some/most) bots

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/2d4af7be9e8a92ebbbc4242b
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Reduce contention on protected-int thread_count

We can capture the new value upon atomic-decrement, use it

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/4090d823bba9fa4630bd79c2
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Solve the active_clients exceeds configured max_clients issue

e.g. with [Web] max_clients configured for 200, the following could occur: sbbs: web 0522 HTTP [34.45.142.114] Session thread terminated (220 clients, 378 threads remain, 128627 served)

The issue was that the active_client count is incremented in the http_session_thread(), but was being checked in the main web server/listening thread.

So now we'll check in both threads, but allow more HTTPS/TLS client threads
(10 more) than the configured max, to allow for successfull sending of error 503 (up to a point), while HTTP (non-TLS) connections exceeding the configured max will be immediately dropped without creating a session thread.

We now no longer increment the client highwater mark for connections that exceed the maximum.

Also fix send_error() to not log the Connection: close\r\nContent-Length: 0\r\n portion of 503 errors.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/1f480068adc0ac59c5b4e663
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Apply max connections per IP limit to filter-exempted IPs

This exemption could (did) cause confusing "works for me" situations when testing max concurrent connections settings that may fail for others.

So, just because an IP address is listed in ctrl/ipfilter_exempt.cfg, no
longer means that clients at that IP are exempt from concurrent connection limits (from a single IP address).

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/c0c3dbdf76d91f155a9371ca
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Revert "Apply max connections per IP limit to filter-exempted IPs"

This reverts commit 1f480068adc0ac59c5b4e6634dc827c52721a7da.

The other servers exempt ipfilter_exempt.cfg listed hosts still and it looks like I really need gitlab to be exempt from the concurrent connections limit for (all my) webhooks to work reliably since they run in parallel and I can't seem to configure that behavior in gitlab.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/a43ca30ea674ac77ca98d74e
Modified Files:
src/sbbs3/websrvr.c
Log Message:
Pad "HTTP" to 5 chars for protocol field in log messages

... aligning display for easier reading with non-proportional fonts.

Includes the client's protocol and IP address in JS log messages/errors.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net