You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2021/10/07 12:58:00 UTC

[jira] [Closed] (TINKERPOP-2616) Provide better exceptions with SSL related failures

     [ https://issues.apache.org/jira/browse/TINKERPOP-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Mallette closed TINKERPOP-2616.
---------------------------------------
    Fix Version/s: 3.5.2
                   3.4.13
                   3.6.0
         Assignee: Stephen Mallette
       Resolution: Done

> Provide better exceptions with SSL related failures
> ---------------------------------------------------
>
>                 Key: TINKERPOP-2616
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2616
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.4.12
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Minor
>              Labels: breaking
>             Fix For: 3.6.0, 3.4.13, 3.5.2
>
>
> Propagate SSL exception to the client. Currently, if an error occurs during connection setup, client observes a generic “connection failed error”. This is because server has no mechanism to send an exact error to the client since the connection was never setup. The idea is to use WebSocket error codes to provide a more specific error to the client.



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