[CXF-4762] HTTPS does not work with asynch client unless you specify port number

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.1, 2.7.2
• Fix Version/s: 2.7.3
• Component/s: Transports
• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Øystein Grimstad
• Created: 17/Jan/13 15:44
• Updated: 28/Feb/13 17:27
• Resolved: 24/Jan/13 17:23

Description

I´m trying to get CXF in combination with HttpAsyncClient to talk to my server over HTTPS. What I found is that when I try to consume the url https://myserver/service, CXF/HttpAsyncClient will actually try to talk TLS to my server on port 80.

Digging around in various source code, I found that the getTarget() method in CXFHttpAsyncRequestProducer is a bit unfortunate. It seems to be hard coded to use port 80, unless a port is specified. I´m suggesting that instead of hard coding port 80, CXFHttpAsyncRequestProducer should be looking at the scheme registry to find an appropriate port or just set the port to -1. In case it returns -1, HttpAsyncClient will do a lookup in the scheme registry to find default port for the requested scheme (ie. http=80, https=443)