You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add connection and request limiting configuration options (#153)
* feat: add connection and request limiting configuration options
- Add -max-requests-per-tunnel flag to limit queued requests per tunnel (default: 20)
- Add -max-clients-per-token flag to limit concurrent clients per token (default: unlimited)
- Implement client count tracking with automatic cleanup on disconnect
- Update /_stats endpoint to display configuration limits and client counts
- Add comprehensive tests for both limiting features
- Update documentation with usage examples and monitoring information
These features address issues #146 and #137, providing better resource control
and preventing unauthorized token sharing or connection conflicts.
Closes#146Closes#137
* feat: add connection and request limiting configuration options
- Add -max-requests-per-tunnel flag to limit queued requests per tunnel (default: 20)
- Add -max-clients-per-token flag to limit concurrent clients per token (default: unlimited)
- Implement client count tracking with automatic cleanup on disconnect
- Update /_stats endpoint to display configuration limits and client counts
- Add comprehensive tests for both limiting features
- Update documentation with usage examples and monitoring information
These features address issues #146 and #137, providing better resource control
and preventing unauthorized token sharing or connection conflicts.
Closes#146Closes#137
This is useful when you want to ensure only a single client instance per token is allowed, preventing unauthorized token sharing or connection conflicts.
WStunnel server provides a `/_stats` endpoint that displays information about connected tunnels. When accessed from localhost, it provides detailed information including:
238
274
239
275
- Number of active tunnels
276
+
- Server configuration limits
240
277
- Token information for each tunnel
241
278
- Pending requests per tunnel
242
279
- Client IP address and reverse DNS lookup
243
280
- Client version information
244
281
- Idle time for each tunnel
282
+
- Current client counts per token (when limits are configured)
0 commit comments