cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Assigned] (CXF-4762) HTTPS does not work with asynch client unless you specify port number
Date Thu, 24 Jan 2013 17:07:14 GMT


Daniel Kulp reassigned CXF-4762:

    Assignee: Daniel Kulp
> HTTPS does not work with asynch client unless you specify port number 
> ----------------------------------------------------------------------
>                 Key: CXF-4762
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.7.1, 2.7.2
>            Reporter: Øystein Grimstad
>            Assignee: Daniel Kulp
> 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)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message