Connections will not closed even though header sent to close explicitly

[SamathaUppula]

Steps to Reproduce:

1. Create any micronaut application
2. Try to connect any api endpoint by using micronat http client

3. Send a header in the request "connection:close"

   Expected Behaviour:

Connection should be closed after getting the response.

Actual Behaviour:

Connection will never get closed and becomes a persistence connection.

Issue description: This is the code in RoutingInBoundHandler

// default Connection header if not set explicitly

            boolean expectKeepAlive = nettyResponse.protocolVersion().isKeepAliveDefault() || httpRequest.getHeaders().isKeepAlive();
            HttpStatus status = nettyHttpResponse.status();
            if (!expectKeepAlive || status.getCode() > 299) {
                nettyHeaders.add(HttpHeaderNames.CONNECTION, HttpHeaderValues.CLOSE);
            } else {
                nettyHeaders.add(HttpHeaderNames.CONNECTION, HttpHeaderValues.KEEP_ALIVE);
            }
        }```

For HTTP_1_0 isKeepAliveDefault is false but for HTTP_1_1 isKeepAliveDefault is true. According to micronaut gitter discussion HTTP_1_1 is in use so isKeepAliveDefault is always true which is not letting the connection to close.

https://gitter.im/micronautfw/questions

[jameskleeh]

What should happen when both the request and response contain the header and they are different?

[jameskleeh]

@SamathaUppula Are you using a client with a connection pool? Can you include a sample of how the client is being created and the request sent?

[jameskleeh]

Closed due to a lack of feedback