A modern programming language that makes developers happier.

kotlinlang

<@U0M0EAG90> thanks for the PR - we'll look at getting it in soon - we just want to be extra careful as we've had the opposite experience - servers rejecting host headers when there is a port set. Out of interest, what is the server that rejects it without the port?

It's an F5's BigIp proxy. But I guess it's just a matter of configuration. Our network team could probably have configured it to accept the request without a port on the Host header.

Excerpt from RFC 2616:
```
A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP URL)
```
So if I want to connect to `<http://my.host.com:81/a/path/>`, the Host header must have the port information, otherwise it would imply port 80.