Files
Rafael Cepeda b60d141920 Document when channel.remoteAddress field can be nil (#3456)
Added extra documentation to `channel.remoteAddress` field to capture a
scenario where this field might be `nil`

### Motivation:

It is somewhat common for users to have code like
`channel.remoteAddress!` in their implementation, as it is a reasonable
assumption to think a socket connection will have an associated remote
address. However, in at least one known situation this might not be the
case. When that happens, user's code might crash due to the force unwrap
of the optional field.

### Modifications:

Introduced more documentation to make it clear that users should be
prepared to handle the `nil` scenario.

### Result:

Less frequent mishandling of `channel.remoteAddress`.
2025-12-01 11:09:56 +00:00
..

NIOHTTP1Client

This sample application provides a simple echo client that will send a basic HTTP request, containing a single line of text, to the server and wait for a response. Invoke it using one of the following syntaxes:

swift run NIOHTTP1Client  # Connects to a server on ::1, port 8888.
swift run NIOHTTP1Client 9899  # Connects to a server on ::1, port 9899
swift run NIOHTTP1Client /path/to/unix/socket  # Connects to a server using the given UNIX socket
swift run NIOHTTP1Client echo.example.com 9899  # Connects to a server on echo.example.com:9899