[
https://issues.apache.org/jira/browse/HTTPCLIENT-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536123#comment-13536123
]
Nicolas Richeton commented on HTTPCLIENT-1282:
----------------------------------------------
I made a quick check : we already construct requests URI with the virtual host,
but this information is not used by HttpClient for cookie validation at least
on 4.2.2.
At the API level, I think you are right URI and target host are enough for our
usecase.
At the behavior level, we still have an issue : Only target host is used for
cookie validation, and not the URI or any additional Host headers.
Should we move this discussion to another bug ?
Nicolas
> When using Virtual host, there is no way to use the default port
> ----------------------------------------------------------------
>
> Key: HTTPCLIENT-1282
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1282
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.2.2, 4.2.3
> Reporter: Nicolas Richeton
>
> The following change automatically adds a port to the provided virtual host :
> https://issues.apache.org/jira/browse/HTTPCLIENT-1092
> This is an issue, because you can no longer use a virtual host with default
> port, but web applications often fixes urls by redirecting to the canonical
> url (which does not include port). It makes impossible to reach page content
> as we are getting only redirects.
> This would need to revert this update.
--
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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
