[
https://issues.apache.org/jira/browse/AXIS2-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-6047.
------------------------------------
Resolution: Fixed
This was fixed as part of the migration from HTTPClient 4 to
HTTPClient 5 (AXIS2-6051). The old HTTPClient4TransportSender class
has been removed entirely.
The replacement HTTPClient5TransportSender (via RequestImpl) always
constructs HttpHost with the explicit port, ensuring the Host header
includes non-standard ports as required by the HTTP spec. Existing
tests in HTTPSenderTest verify this behavior for GET, POST, and other
methods (e.g., asserting Host: localhost:<port>).
> Missing Port in the Host header of the requests coming from
> HTTPClient4TransportSender implementation.
> -------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-6047
> URL: https://issues.apache.org/jira/browse/AXIS2-6047
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.7.9
> Reporter: yuvaraj
> Priority: Major
> Fix For: 2.0.1
>
>
> The host header should have a port in all cases where the port is
> non-standard:
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Host
> Host header, which is in the requests coming from
> org.apache.axis2.transport.http.impl.httpclient4.HTTPClient4TransportSender
> implementation does not contain the configured port number even when it is
> different from the default ports for HTTP (80) and HTTPS (443). This affects
> the correct load balancing that is based on the Host header.
> Note: It works good (Host header contains port ) with the default
> implementation org.apache.axis2.transport.http.CommonsHTTPTransportSender
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
