[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337062#comment-17337062
 ] 

Babu Reddy commented on HTTPCLIENT-1698:
----------------------------------------

[~michael-o], We are currently using Rest Easy Client(3.0.4), this version of 
the client is dependent on HttpClient and Core (4.x.x). I am not able to test 
if Master / 5.0.Alpha1 without making big changes to dependencies and the code. 
Is it possible to back port the code if the fix is already committed?

> Hostname verification fails when using URL with literal IPv6 address
> --------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1698
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1698
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.4.1
>            Reporter: Jens Borgland
>            Priority: Minor
>             Fix For: 5.0 Alpha1
>
>
> Repro steps:
> # Set up an HTTPS server with proper certificates (with the IPv6 address as a 
> subject alternative name)
> # Set up HttpClient with the DefaultHostnameVerifier
> # Try to contact the server using the IPv6 address (in square brackets in 
> accordance with RFC 2732) in the URL, something like: 
> https://[2001:db8::2:1]:443/example
> Result: 
> An SSLPeerUnverifiedException (note the square brackets):
> {noformat} 
> Host name '[2001:db8::2:1]' does not match the certificate subject provided 
> by the peer <redacted>
> {noformat} 
> *Expected*: 
> The hostname verification to work 
> ({{org.apache.http.conn.ssl.SSLConnectionSocketFactory}} should feed just the 
> IP address, without square brackets, to the HostnameVerifier).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to