Motivations:

reactor.netty.http.server.DefaultHttpForwardedHeaderHandler should use only the reactor.netty.http.server.ConnectionInfo public API if we want the custom parsers to have the same information as us. Now, in #2761 PR , the fix done in the DefaultHttpForwardedHeaderHandler method is using some private constructors from the ConnectionInfo when parsing a X-Forwarded-Port header. This breaks the contract because people cannot then do the same using their own custom handlers.

Related to #2751

Modifications:

• Introduced a new withHostAddress(InetSocketAddress hostAddress, String hostName, int hostPort) method in ConnectionInfo, and the DefaultHttpForwardedHeaderHandler is now using it.
• DefaultHttpForwardedHeaderHandler is still using ConnectionInfo.getHostName() , which is not public but people can implement their own logic in order to obtain the host name.
• a new CustomXForwardedHeadersHandler test class with a package that is different than reactor.netty.http.server has been introduced and is meant to check that people can implement the same logic for parsinx X-Forwarded headers.
• All xForwarded* tests are now run with both DefaultHttpForwardedHeaderHandler as well as with new CustomXForwardedHeadersHandler.