Logging
The Logging settings determine what record is kept of the requests the server receives, and how much of that record is surfaced while you work. They affect reporting only: neither option changes which requests are accepted, nor what a connected client is permitted to do.
When enabled, each accepted request is written to the log — the operation that was invoked together with the arguments it was given. This is the audit trail. It is what allows a session to be reconstructed after the fact, and it is the first place to look when a client's behaviour needs to be explained.
The record covers the content of a request, not merely its name. Where a client submits Python source for execution, the submitted code is logged in full. Keep this in mind if logs are collected centrally or passed on for support purposes: they can contain file paths, scene data and anything else a client transmits.
Disabling the option reduces the volume that is written, at the cost of leaving accepted requests unrecorded.
Show Rejected Calls in Console
A rejected call is a request the server declines rather than answers. Rejections arise for several distinct reasons:
| Reason | Typical situation |
|---|---|
| Missing or incorrect authentication token | A request arriving with no token or an unrecognised one — on a reachable port commonly an unsolicited probe rather than a configured client |
| Source address not permitted | A remote client on a host that is absent from Whitelisted IPs |
| Origin not permitted | A browser-based client whose origin is absent from Browser Client Origins |
| Capability switched off | A request to run Python while the corresponding option in the Security settings section is disabled |
When this option is enabled, each rejection is reported in the Cinema 4D Console as it occurs. It is disabled by default: a server reachable over a network attracts unsolicited requests, and in normal operation the resulting entries add noise rather than insight.
Enable it while diagnosing a connection that does not behave as expected. A client that cannot connect at all, or that reports a tool as unavailable, will usually produce an entry naming the reason — which is considerably quicker than inferring the cause from the client side alone.