Oct
28
2026
New inbound connection log
- The logging of inbound HTTP connections has been redesigned to simplify the analysis of connection problems. Instead of a single log file (log/yyyy_MM_dd.jetty.request.log), a separate file is now written for each inbound request in the directory log/yyyyMMdd/inboundhttp. Each inbound connection log file contains all information required for the analysis, including the processing state, the HTTP status code, sender, TLS protocol and cipher suite, HTTP headers and the size of request and response. Connections that are rejected by the embedded HTTP server, e.g. because of a failed TLS handshake, an unknown receipt URL or missing authorization, are logged as well. The logging is intended for troubleshooting and can be enabled and disabled at runtime in the server settings, no restart is required. The log files are deleted automatically after two days.
- A problem with the REST API licensing has been fixed.