Feature request: periodic log entries during large file transfers

[NinoSkopac]

When downloading large files (e.g., a 1TB file), it would be helpful to receive periodic log entries at defined intervals (e.g., every n seconds) that report on the progress of the file transfer. Instead of a single log entry at the end indicating the completion of the transfer, the system should generate multiple log entries during the transfer, each corresponding to a specific chunk of data delivered.

This feature would provide real-time visibility into the progress of large file transfers, making it easier to monitor and manage the download process, especially in environments where continuous feedback is crucial.

Totally fine if this is behind a flag.

Thank you and have a great day!

[zh-jq-b]

Do you want this feature just for layer-7 HTTP request/response, or for all of the layer-4 tunnel connections?

[NinoSkopac]

Layer 4, please. I do love having socks5, it's so much more efficient. In my tests it consumes way less data for the same URL compared to http proxy.

Design note: please do not log the total bytes received on top of chunks' logs.

Example if downloading a 1GB file and my speed was 1MB/s:

1. log received 1MB
2. log received 1MB
3. ...
4. do not log 1GB received

Thank you Mr. Zhang!!!

[zh-jq]

For tunnel connections, we don't known whether it's downloading files. What can be done is that, log when reading/writing to client connections at some nearly fixed time interval.

[NinoSkopac]

That works!

[NinoSkopac]

Note: auth and its refresh interval must be respected. As in, a user could be valid now, but invalid at a later chunk/interval. In that case the connection must be terminated.

Should this be a separate issue? Is this already implemented? (I haven't tested.)

[zh-jq-b]

Note: auth and its refresh interval must be respected. As in, a user could be valid now, but invalid at a later chunk/interval. In that case the connection must be terminated.

Should this be a separate issue? Is this already implemented? (I haven't tested.)

You can set a user to blocked state and then it will be blocked after idle_check_interval (5min by default).