[jira] Commented: (WINK-242) Support SSL Hostname Verifier Bypass

["David Johnson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WINK-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968886#action_12968886 ] 

David Johnson commented on WINK-242:
------------------------------------

The fix is not complete. In addition to the bypass in processRequest(), you also have to bypass hostname verification in createResponse(). I will attach a patch to fix this.

> Support SSL Hostname Verifier Bypass
> ------------------------------------
>
>                 Key: WINK-242
>                 URL: https://issues.apache.org/jira/browse/WINK-242
>             Project: Wink
>          Issue Type: New Feature
>    Affects Versions: 1.1
>         Environment: Doesn't matter
>            Reporter: Andrew Spyker
>            Assignee: Mike Rheinheimer
>            Priority: Minor
>         Attachments: WINK-242.patch
>
>
> It is incorrect, but common, for web sites to have SSL certs that are signed by localhost with localhost as the CN/hostname, but then are deployed on real websites like w3.internal.example.com.  If you try to connect to one of these with Wink you get:
> Exception : java.io.IOException: HTTPS hostname wrong: should be <localhost>
> You'll see extensive discussion and how to fix at:
> http://forums.sun.com/thread.jspa?threadID=521779
> You'll also see commercial products supporting this behavior as well like:
> http://www-01.ibm.com/support/docview.wss?uid=swg1PK24500

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.