Known Issues

Known Issues and Limitations

What Rony.Net 1.5.0 does not do, or does in a way that can surprise you. None of these breaks a normal test; they are listed so you don't have to find them yourself. For problems with a known answer, see Troubleshooting.

Mock server

• RefuseConnections() can reset a client that is connecting at that moment. A client whose connection was completed by the clients that are already waiting, so only a client whose connect completes at that very moment may be reset instead of refused. This cannot be closed completely: wait with WaitForConnectionAsync() for the clients you expect before refusing. See Simulating Failures.
• Received requests are kept until Mock.Reset(), connection records until the server is disposed, unless you cap them. That is what Should(), ReceivedRequests and Connections read. A server that runs for a long time grows with the traffic it receives; set Mock.MaxReceivedRequests and MaxConnectionRecords (the standalone tool does by default). See Verifying Requests. With StateScope.Connection on UDP, one small entry per distinct client address is kept for the whole run (TCP entries are removed with the dropped connection record).
• No limit on buffered data unless you set one. A client that never completes a message makes the server buffer what it sends. Set MaxBufferedBytes on the listener when the client is not your own code. Servers from a configuration file default to 16 MiB. See Connections and Framing.
• A regular expression given in code has no timeout. A slow pattern delays all clients, because rules are matched one request at a time. Patterns from a configuration file time out after one second.

TLS

• A rejected client certificate does not fail at the same moment on every system. Depending on the operating system and the TLS version, the client sees the rejection while connecting or on its first read or write. Wait for it on the server side (the log or ConnectionFailed). See SSL and TLS.
• Mutual TLS accepts any presented certificate unless you set ClientCertificateValidator. The chain is not validated and revocation is not checked: test certificates are self-signed. A configuration file cannot set a validator.
• TestCertificate.CreateSelfSigned() adds nothing to a certificate store, but the .NET runtime may keep the private key outside the process: a temporary keychain file on macOS, a temporary key container on Windows. On macOS the key of such a certificate cannot be exported to a PFX file.
• No TLS on Unix domain sockets or UDP.

Unix domain sockets and IPv6

• ResetAsync() and ResetConnection() are a plain close on a Unix socket. There is no RST; the client sees an end of stream or an error, depending on the platform.
• A refused Unix-socket client gets a platform-dependent error, not necessarily "connection refused", because the socket file is removed while connections are refused.
• Address and Port mean nothing for a UnixSocketServer (IPAddress.None and 0); use Path.
• In dual mode, IPv4 clients appear with IPv4-mapped addresses such as ::ffff:127.0.0.1.
• See Servers.

Record and replay

• TCP and TLS only; the proxy does not relay UDP.
• Replay is order-dependent. A reply that depends on earlier requests replays correctly only when the client sends its requests in the recorded order.
• Recorded times are not replayed as delays.
• A recording and the proxy's log contain everything on the wire, including credentials and tokens.
• See Record and Replay.

Configuration files

• A file cannot express everything the API can: no response functions or predicates, no truncated, corrupted, chunked or throttled responses, no failing handshakes, no certificate validators, no custom framing. See Not available in files.
• A udp server binds its port when the file is loaded, not when the server starts, as new UdpServer(...) does.
• tls.password is plain text in the file.
• A slow regular expression delays all clients until its one-second timeout.
• See Configuration Files.

Standalone server (rony)

• For development and test networks only. No limit on connections, idle time or handshake time, and rony record keeps its whole recording in memory until it stops (run and replay keep only the last 10000 requests, see --keep). See Limits and security.
• rony run --watch reloads the rules only. A change to the server section (address, port, transport, framing, TLS) needs a restart.
• The control endpoint reads and sets only the server-wide state. With "stateScope": "connection" the state commands reply with an error; see Standalone Server.
• The control endpoint has no authentication. It listens on 127.0.0.1 unless you pass --control-address; anyone who can reach it can read the received requests (credentials included) and change the state.
• A control command line longer than 1 MiB closes that control connection.
• The Testcontainers module does not support unix configurations, needs an extra port binding for udp, does not copy files the configuration names (a certificate), and needs the image of its own version, which exists from 1.5.0. See From a .NET test with Testcontainers.
• rony record does not check the target before it starts. An unreachable target shows up as a logged error per connection.
• A recording stores messages in the order they arrived. A client that sends before the server's greeting arrives gets the greeting recorded as the reply to its first request; record with the client as it normally behaves.
• In a container the configuration must listen on 0.0.0.0 (or run with --address 0.0.0.0); the default 127.0.0.1 cannot be reached from outside the container.
• See Standalone Server.

Found something that is not on this page? Please open an issue.