You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/10/05 13:45:00 UTC

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

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

ASF GitHub Bot commented on TINKERPOP-2616:
-------------------------------------------

spmallette merged pull request #1479:
URL: https://github.com/apache/tinkerpop/pull/1479


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@tinkerpop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Priority: Minor
>              Labels: breaking
>
> 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)